Include blueapi version in metadata

[ZohebShaikh]

Currently blueapi version is not included in the metadata this can be helpful to give warnings when blueapi-cli is talking to a different version of blueapi server. Currently the entire application in package as one so the blueapi-cli and blueapi server are only guaranteed to be compatible with the same version.

Acceptance Criteria

• API version included in the metadata
• Blueapi package version included in the metadata
• Warning added when blueapi-cli is talking to a different version of blueapi-server

[abbiemery]

Which metadata is this referring to? If it's just for the client/CLI could we include a version header in responses?

[ZohebShaikh]

Currently from a server you only get the REST_API_VERSION

My suggestion was to add the version for blueapi-server i.e currently 1.12.0 to the header and the same version for the blueapi-client as well

This will let us make a check in the blueapi-client that gives a warning if you are using blueapi-cli version A but the server that you are talking to is blueapi-cli version B they might not work all the time

At the time when this issue was created the blueapi-server was getting a lot of config changes and old blueapi-cli was not compatible with it as it was a older version, so you get errors when you try and run the cli.
Sometime it starts up and you get errors afterwards