chore: improve grpc tooling and upgrade setup-go to v3

[lvrach]

Description

This PR is addressing the following issues:

• It was not straight-forward how to generate grpc & proto files. I have added the command in Makefile
• Some proto files were generated with different versions using github.com/golang/protobuf/proto, which is suppressed by google.golang.org/protobuf. I've updated all of them.
• No CI process was validating that proto files were indeed generated. I have added a verification step in github-action.

While adding the verification step, I noticed that GOPATH/bin was not added to PATH. Something that setup-go v3 is solving:

setup-go v3 also takes care of caching. Thus I've removed actions/cache@v2 step and used setup-go v3 in all methods.

Notion Ticket

https://www.notion.so/rudderstacks/proto-CI-improvements-24f0127f8e614aabab45cd17c14bbf5d

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[lvrach]

Backwards compatibility is no longer needed.

[codecov]

Codecov Report

Base: 43.91% // Head: 43.98% // Increases project coverage by +0.06% 🎉

Coverage data is based on head (7323301) compared to base (26b218c).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2553      +/-   ##
==========================================
+ Coverage   43.91%   43.98%   +0.06%     
==========================================
  Files         187      187              
  Lines       39082    39082              
==========================================
+ Hits        17163    17190      +27     
+ Misses      20838    20811      -27     
  Partials     1081     1081              

Impacted Files	Coverage Δ
services/stats/stats.go	88.48% <0.00%> (-1.82%)	⬇️
processor/processor.go	72.05% <0.00%> (+0.82%)	⬆️
enterprise/reporting/reporting.go	9.77% <0.00%> (+1.43%)	⬆️
enterprise/suppress-user/suppressUser.go	82.71% <0.00%> (+1.85%)	⬆️
config/backend-config/namespace_config.go	73.95% <0.00%> (+3.12%)	⬆️
enterprise/reporting/setup.go	52.38% <0.00%> (+14.28%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[lvrach]

here is a caveat, it is hard to enforce protoc version is the same in all environments.

I could install the latest proto version in github actions and ubuntu is using a match older version by default.

What I noticed however is that the only difference is only the comment with the version. Thus, there is no real impact on the output if we compile from different protoc versions and if there is we can detect on our CI.

Another option is to use a docker image to generate the protoc files as @fracasula had done in the past.

[fracasula]

On CI I don't mind, either way it's fine so whatever it works for you 👍

I like the Docker approach mostly for the Makefile for recipes that we are meant to run locally. Mostly for cases like with protoc where a go install isn't enough. I use OpenSuse for example and I have to install protobuf-devel in order to be able to generate the files. The problem arises if somehow you want to install a different version of protoc.