Ensure matching modules with metadata when requested

[pselle]

When explicitly requesting a module with metadata information (ex. 1.0+abc), go-version does not differentiate between versions based on build number. According to semver:

Build metadata SHOULD be ignored when determining version precedence.

So when comparing versions (including on equality) go-version will not factor in build/metadata, since it generally follows this spec.

As such, this PR adds a bit of logic to make sure that Terraform matches versions exactly when exact matches are requested for a version with metadata.

Addresses #20814

[apparentlymart]

Doing this at the Terraform layer seems like a nice compromise to allow us to fix it without potentially impacting other go-version users. 👍

I left a couple questions inline.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.