GO: Adding Route support

[janhavigupta007]

No description provided.

[Yury-Fridlyand]

CI is red, something wrong in rust code.

I propose to split this PR into multiple parts. You can develop all together, but split later in order to keep PRs small, reviewable and contain only one feature.
0. Wait for #2803 merge and rebase
2. Add INFO command
3. Add Routes
4. Add fixes for PING

Why INFO is important? It allows you to validate how command was actually routed:

$ redis-cli info server | grep tcp_port
tcp_port:6379

With INFO you can test routing feature

[janhavigupta007]

CI is red, something wrong in rust code.

I propose to split this PR into multiple parts. You can develop all together, but split later in order to keep PRs small, reviewable and contain only one feature. 0. Wait for #2803 merge and rebase 2. Add INFO command 3. Add Routes 4. Add fixes for PING

Why INFO is important? It allows you to validate how command was actually routed:

$ redis-cli info server | grep tcp_port
tcp_port:6379

With INFO you can test routing feature

I undestand that the INFO command is more suitable for checking Route functionality. My proposal is to only include Route implementation in this PR and doing the validation via INFO and PING implementations in a separate PR to keep the changes small. Hope that's okay.

[Yury-Fridlyand]

LGTM
Please make a follow up PR with info, so we can verify this feature.

[Yury-Fridlyand]

Please update PR description and title