Adding gRPC Client generation from the existing protobuff files

[jenspapenhagen]

With bufhttps://github.com/bufbuild/buf,
implementing it for other programming languages was much easier than expected.

first Draft

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rrobetti]

@jenspapenhagen what is the goal of this PR?

[jenspapenhagen]

To use OJP in other programming languages, such as Go, Rust, or Node.js.
Because not all of a company's microservices are written in Java, but connect to a DB

[rrobetti]

@jenspapenhagen if this is only compiling the gRPC protocol, we won't be committing the result of the grpc compilation.

For comparison, in Java we don't have the grpc client stubs committed; they are compiled every time the client is compiled. This is standard for gRPC. Having stubs of a gRPC interface compiled is extremely cheap; the challenges in creating a client in another language are:
1st - To find the right interfaces to implement; for example, .NET uses ADO.NET, can we create an implementation of ADO.NET that using the OJP gRPC protocol to interact with OJP Server?
2nd - Use JDBC integration tests we currently have as a starting point to test the new client.
3rd - Analyse how concerns like transactions, load balancing, and failover can be implemented in the new interfaces.

Maybe repurpose this PR to do an attempt to implement a module for a new client; start small with a simple CRUD integration?