chore: update to go-licenses/v2

[iamjoemccormick]

What does this PR do / why do we need it?

Required for all PRs.

While we only used it in CI checks, when we switched to running/managing go-license using go tool in #270 this added its dependencies to our go.mod file which flagged the current version as having multiple security vulnerabilities. I upgraded it to the latest version which also notably added support for instances where there are multiple licenses in one LICENSE file.

Related Issue(s)

Required when applicable.

Where should the reviewer(s) start reviewing this?

Only required for larger PRs when this may not be immediately obvious.

Are there any specific topics we should discuss before merging?

Not required.

What are the next steps after this PR?

Not required.

Checklist before merging:

Required for all PRs.

When creating a PR these are items to keep in mind that cannot be checked by GitHub actions:

• Documentation:
  • Does developer documentation (code comments, readme, etc.) need to be added or updated?
  • Does the user documentation need to be expanded or updated for this change?
• Testing:
  • Does this functionality require changing or adding new unit tests?
  • Does this functionality require changing or adding new integration tests?
• Git Hygiene:
  • Do commits adhere to Conventional Commits?
  • Is the commit history squashed down reasonably?

For more details refer to the Go coding standards and the pull request process.

[swartzn]

LGTM