Properly handle SUBSCRIBE errors

I've recently learned that SUBSCRIBE may error under circumstances other than a syntax error. For instance, when using ACL, the server returns an error if the user doesn't have access to the requested channels.

I think we need to improve how we handle these errors. Currently, in the best scenario, they're interpreted as pushes as put into the receive response. But if other commands are on the flight, they will be interpreted as errors to these commands, completely messing up the connection. I can see attackers somehow crafting channel names to exploit this.

I've seen that SUBSCRIBE immediately returns a push with a certain response. My proposal is attempting to identify this push (or the corresponding error), and fail the request if an error is seen.

Trace the SUBSCRIBE request and receive-response handling described in the issue, then reproduce an ACL-denied subscription while other commands are in flight. Done means the subscription request receives the error, subsequent command responses remain correctly associated, and the connection is not desynchronized.

Written by the indexing model from the issue text.