Update project to log v2
What does this MR do and why?
The library the project uses for logging has v2 now: https://github.com/charmbracelet/log/blob/v2.0.0/UPGRADE_GUIDE_V2.md.
It didn't require any code changes in logging itself, but requires a newer version of Go (https://github.com/charmbracelet/log/blob/32debe4429a80bef14efe989fc4829a6b9beac18/go.mod#L3). This meant we also needed to update the version of golangci-lint so that it was compatible with the newer Go. Some code changes were required to pass this check: https://staticcheck.dev/docs/checks/#QF1012.
It's probably good for the project to move forward with some of these dependencies from time to time. This will bring this project's version of Go to the second-most-recent minor version, so wouldn't be considered bleeding edge.
How to set up and validate locally
- Configure a local GitLab Docs environment.
- Check out this branch.
- Run
make go-tests - Run
make lint-go - Run
make build-data - Run
make test-mermaid - Run
make update-all-docs-projects
Merge request acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
- I have evaluated the MR acceptance checklist for this merge request.
- If this MR changes how markdown is interpreted, share this MR in the
#tech-docs-localizationslack channel. The translation tooling might need to be updated, for example if new syntax is added or existing syntax rendering is changed.