chore(deps): update module version to match tag major version

[smcavallo]

Signed-off-by: smcavallo [email protected]

Description

Update module version to match tag version.

The ultimate goal is to allow this module to be published to the go artifact registry
The latest current version there is 2.50.2 which is the last version 2 which was tagged.
See on the registry - https://pkg.go.dev/github.com/newrelic/terraform-provider-newrelic/v2
See the tags - https://github.com/newrelic/terraform-provider-newrelic/releases?page=10

Bumping to /v3 to match the tag version and enable an artifact to be published.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

Please delete options that are not relevant.

• My commit message follows conventional commits
• My code is formatted to Go standards
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes. Go here for instructions on running tests locally.

How to test this change?

Please describe how to test your changes. Include any relevant steps in the UI, HCL file(s), commands, etc

• Step 1
• Step 2
• etc

[vagrawal-newrelic]

hey @smcavallo Thank you for your contribution. Could you please share if there was a specific reason or any particular issue that prompted you to update the toolchain version?

[smcavallo]

Hi @vagrawal-newrelic - yes - it was because some of the community images were patching the toolchain version to address this CVE -> https://nvd.nist.gov/vuln/detail/CVE-2024-24790#range-13244817
See - https://go.dev/doc/devel/release#go1.22.minor

Updating the toolchain version was purely driven by addressing that CVE on my part. There was no functional reason for the update. I can revert back to go1.22.6 and submit this change in a separate PR if that would make sense. Please let me know. Thank you so much for reviewing this PR.