Detect incompatibility and raise a relevant exception about typedb-driver-nodejs

[vmax]

@sorsaffari (cc @haikalpribadi @lolski) as this feature seems to be needed for all clients, should we make a gRPC endpoint in server that would tell minimal version of client needed to connect to that server?

[flyingsilverfin]

@vmax I was thinking each client would maintain a compatibility table rather than server maintaining one per client (since each client can have different versions). The server just needs to return its version when we open a client I think!
This would entail just having a new version endpoint that we check when opening a channel in each client would be the most general solution, what do you think?

[vmax]

@flyingsilverfin let me correct myself a bit. Server should report minimal version of protocol that client should implement in order to connect to it.

Say, we establish that current version of protocol that latest server and client implement is v1.
Then, when we need to introduce incompatible changes in server, we'll have to bump server to report v2 as the minimal protocol it supports — therefore, clients that only implement v1 would be rejected a connection.

[haikalpribadi]

I agree with @vmax. It's a good idea for the server to report the protocol version it serves, and the client validates if they are using that protocol. It has to be one to one anyways. cc: @sorsaffari @flyingsilverfin @lolski

[alexjpwalker]

We should hold on to the potentially useful discussion in this issue, however it is a duplicate of vaticle/typedb-driver#25 (it can be assumed that we will implement this feature in all clients).