CI, Golint Check before building PR

[chenchanglew]

Is your feature request related to a problem? Please describe.
I had a Golang lint error after 20 minutes of docker build. Maybe we can add a new Golint checking before building docker image in CI.

Describe the solution you'd like
Current CI Flow:

Set up job
Run actions/checkout@v4
Run dorny/paths-filter@v2
build dev image
fetch dev image
run make inside dev container
....

Suggest CI Flow:

Set up job
Run actions/checkout@v4
Run dorny/paths-filter@v2
golint checking
build dev image
fetch dev image
run make inside dev container
....

Describe alternatives you've considered
Or any step before run make inside dev container

[mbrandenburger]

Need to check if we can run the check target before build.

The current order is defined here:
https://github.com/hyperledger/fabric-private-chaincode/blob/main/build.mk#L20

[mbrandenburger]

Another issue is that we need to generate proto files otherwise the linter is not happy with go and cpp code :/

[mbrandenburger]

@chenchanglew why don't we just checking the generated protos? I don't see a reason why we cannot have the generated protos in the repo; that way we can run the linter before building and testing the entire stack. WDYT?

[yogita-mehta]

Hi @mbrandenburger, I completely agree with your recent suggestion to commit the generated protos to unblock the CI linter. I have my local environment set up and I am already familiarizing myself with the protobuf structures in the repository. I would love to implement this CI workflow change and ensure the linter runs smoothly before the docker build. Could you assign this to me?