.github: add golangci-lint, split PR verification into multiple jobs.

[klihub]

This patch set adds a golangci-lint worklflow. Additionally, it splits PR verification into multiple parallel jobs.

[fmuyassarov]

LGTM.
Is there any reason to split out the golangci-lint into its own workflow file?

[kad]

generally ok, but minor question about golang versions.

[kad]

should it be 1.23.x? or latest 1.22.10?

[klihub]

Let's do that separately, consistently for everything in the repo, in a single go.

[klihub]

I can file another PR for that.

[kad]

same, should it be 1.23.x or latest 1.22.10?

[klihub]

LGTM. Is there any reason to split out the golangci-lint into its own workflow file?

Well, nothing too specific, really. I wanted for a while now to get rid of that 'project checks' workflow, and split it up to smaller, more granular jobs. And, well... there is never a better time than right now. About golangci-lint, since @kad mentioned the other day that he might want to enable other linters too, I decided to add the new golangci-lint job readily to a new lint workflow.

[fmuyassarov]

LGTM. Is there any reason to split out the golangci-lint into its own workflow file?

Well, nothing too specific, really. I wanted for a while now to get rid of that 'project checks' workflow, and split it up to smaller, more granular jobs. And, well... there is never a better time than right now. About golangci-lint, since @kad mentioned the other day that he might want to enable other linters too, I decided to add the new golangci-lint job readily to a new lint workflow.

maybe we can then add it to the same workflow since there is no separation in terms of when the job should be executed. (Not a blocker though, feel free to ignore it).

[klihub]

LGTM. Is there any reason to split out the golangci-lint into its own workflow file?

Well, nothing too specific, really. I wanted for a while now to get rid of that 'project checks' workflow, and split it up to smaller, more granular jobs. And, well... there is never a better time than right now. About golangci-lint, since @kad mentioned the other day that he might want to enable other linters too, I decided to add the new golangci-lint job readily to a new lint workflow.

maybe we can then add it to the same workflow since there is no separation in terms of when the job should be executed. (Not a blocker though, feel free to ignore it).

I prefer to keep it separate. I want to see it as Lint / golangci-lint and not as Verify / golangci-lint in the check summary...