feat: adapt websockets bindings to v3

[jonaslagoni]

Description
This PR adapts the websockets bindings to v3. This first round of review is just for the general structure changes.

TODO right before final review:

• Adapt examples, if any that contain v2 structure.
• Figure out which version change this constitutes

TODO after merge:

• Adapt schema files in spec-schema-repo

Related issue(s)
Related to #182

[fmvilas]

Still concerned about the usage of parameters for headers but left other suggestions too.

[fmvilas]

Suggested change

	<a name="operationBindingObjectQuery"></a>`query` | [Parameters Object][parametersObject] | A Schema object containing the definitions for each query parameter.
	<a name="operationBindingObjectHeaders"></a>`headers` | [Parameters Object][parametersObject] | A Schema object containing the definitions of the HTTP headers to use when establishing the connection.
	<a name="operationBindingObjectQuery"></a>`query` | [Parameters Object][parametersObject] | A Parameters object containing the definitions for each query parameter.
	<a name="operationBindingObjectHeaders"></a>`headers` | [Parameters Object][parametersObject] | A Parameters object containing the definitions of the HTTP headers to use when establishing the connection.

[derberg]

there is no need to release new version of the binding. The fact that we changed schema for parameters, do not mean we should change it for query params and headers. Even in the main spec we still allow schema object for headers.

Parameters from spec are simplified as they are focused on the content of AsyncAPI document. They are used to parametrise and describe dynamic parts of channel name. In case of query params, this is something that describes run time behaviour of the server, so it makes sense to for example specify type: boolean for the sake of better code generation -> https://github.com/asyncapi/spec/blob/master/examples/websocket-gemini.yml#L63-L96

[jonaslagoni]

Alright, that makes sense 👍