create backplane cli

[ripienaar]

I reckon the best is if instead of allowing the agent name to be changed we standardise to backplane, we then create a CLI in go that gets released. It also avoids all the insanity with DDL files

This hugely reduce the on boarding surface area since someone then just need to backplane enroll and once they are on the network can manage their microservices with no ruby stuff needed at all.

In time once a choria CA exist this will create a very low friction setup - one that can even be started from a docker compose file in its entirity

[ripienaar]

Some ideas:

$ backplane exec cron pause -W dc=DC1
$ backplane exec cron resume -W dc=DC1
...

exec would be the default so this would also work:

$ backplane cron pause -W dc=DC1

here cron is a name for the managed backplane - which should map to a sub collective where all instances of a specific backplane should live