[Feature Request] Add the ability to query the version of the client

### Background
We develop an application that is able to run with or without pulsar installed, and for that to happen, we do not link with pulsar client (statically or dynamically).

Instead, we load the pulsar client library at runtime (using dlopen) and use the C-API to do what needs to be done.

This means that it is our customers responsibility to install and configure pulsar, and they *could* use any version.

### Request
Since we don't know the version of the pulsar client library at runtime, we cannot make full decisions on the differences of those versions.
E.g. When trying to use the pattern subscribe with the 2.9.2 client, there was an unhandled exception cancelling the topic refresh thread after unsubscribing. This caused our application to crash. This is now fixed in 3.0, but we want to disable that feature if using an older client.

It would be useful to query the client library as to what version it is.

This would also be useful for our logging so we can see what version a customer has installed, and try to reproduce their environment (note that customers don't always tell you the truth, logging information proves what they tell you).

Another useful feature (again for logging purposes) would be to know what the version of the server/broker the client is connected to. It will help with narrowing down problems and reproducing issues.

Start by reviewing the existing C-API entry points used when the client library is loaded at runtime with dlopen. Determine how the client version and the connected broker version could be exposed for feature decisions and logging, then confirm the expected behavior and API shape with maintainers. Done means both versions can be queried where available and are covered by appropriate tests.

Written by the indexing model from the issue text.