runctl server should reject older runctl clients

[rmg]

When running sl-run from strong-supervisor@1.1.1 connecting with sl-runctl from strong-supervisor@1.1.0 results in the sl-runctl command hanging waiting for a response.

The cause is likely sequence numbers being added to the protocol in 1.1.1.

To mitigate this, the server side of the control channel should close connections that don't follow its expected protocol/format instead of silently dropping the message. This would result in an error on the sl-runctl side instead of hanging.

[rmg]

Tracked it down. Turns out it's not just sequence numbers that were added, but a whole other layer of encapsulation. The listening side of the channel in the problem scenario doesn't even get notification that a request was made because strong-control-channel just ignores the request.

I'll fix this in strong-control-channel by closing the connection when a message isn't one of the known message types and release as a new major version, then rev the dependency in strong-supervisor and anywhere else it is used.