Move runner connections to GRPC

[nehashri]

Currently, we have gRPC support when Gauge runs in the LSP mode (when start from vscode or gauge daemon --lsp). We should support gRPC for execution and completely remove RPC.

For this to be effective, we need to ensure that Gauge works with both TCP and gRPC for awhile. Some plugins may choose to use gRPC and Gauge should establish a connection with these plugins through gRPC. If the plugin doesn't specify its preference TCP should be used by default.

[BugDiver]

The changes which needs to be done

In Gauge

• Figure out if runner has full support for gRPC (for execution/lsp)
• Start the runner and figure out the gRPC server port
• Create a client and register required service (lsp or runner),
• Establish a connection with the Server

In runner

• Add an gRPCSupport property in runner.json
• Implement runner gRPC services.
• Start the gRPC runner at a random port.
• Log the port info on the stdout (gauge captures it to make a connection)
• Add the service handler and wait till terminated

• Dotnet
• Java
• Java (Multithreading)
• Javascript
• Javascript (Multithreading)
• Python
• Ruby

[Debashis9012]

All the above runners have been tested and working as excepted.