fix(versioning/hashicorp): allow v versions from npm

[rarkins]

Changes

Allows v versions instead of throwing

Context

Errors thrown in the hosted app

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

@mcfedr I'm not sure if this is the best way to fix this, but at least it should stop it throwing for values like v4.0.1

[rarkins]

This may fix #19766 if the original fix didn't

[mcfedr]

Interesting that it happens, as npm2hashicorp is only called on the results of hashicorp2npm which ought to remove all "v"s - ice done this as npm spec doesn't allow them, although I notice the implementation of npm is very forgiving

[mcfedr]

Im now thinking throwing wasn't a great idea in a code base that doesn't expect it!

[renovate-release]

🎉 This PR is included in version 34.102.2 🎉

The release is available on:

• GitHub release
• 34.102.2

Your semantic-release bot 📦🚀