{fast: true} does not create correlation ids or waiters
Being {fast: true} is a client thing
- Do not create a special queue
- Since fast was the only option allowed, remove options parameters from the provider
Cleanup: do not reuse the options parameter of the request for the queue options.
It was possible for an API client to pass options with special meaning for the AMQP Gem.
Now we restrict the valid keys and copy them to a new hash
Queue: Do not set :reply_to if we do not have a :correlation_id
Queue: the provider does not send a reply if not needed
WS: Only send a reply if needed
WS: cleanups

The server does not use a single websocket, so I removed the method
(not used anyways, since it always need to manage the ws instance
provided by the callback parameters)

Also, fix a previous mistake and allow (again) request to receive an
explicit web socket (needed by servers)
fast_actions method is no longer needed