documentation for golangci-lint for go project CI

What does this MR do?

[golangci-lint](https://github.com/golangci/golangci-lint) is a configurable
and fast metalinter and is the suggested alternative to the now-deprecated
[gometalinter](https://github.com/alecthomas/gometalinter)

This example CI job will lint only the changes to a new merge request,
allowing projects to switch to `golangci-lint` or adopt stricter linting
rules without breaking CI builds.

For non merge request runs, a fallback revision can be set to lint
changes since that revision, allowing linting on CI runs on the
default project branch.

Related issues

Author's checklist

• Follow the Documentation Guidelines and Style Guide.
• If applicable, update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Apply the documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.