[admin] Validate version format in release workflow

[mx-psi]

Component(s)

No response

Describe the issue you're reporting

We don't do any validation on the version introduced for the prepare-release workflow, but we have some restrictions on the version format as documented here:

opentelemetry-collector-contrib/.github/workflows/prepare-release.yml

Lines 4 to 14 in a4e4fe4

	workflow_dispatch:
	# Determine the version number that will be assigned to the release. During the beta phase, we increment
	# the minor version number and set the patch number to 0.
	inputs:
	candidate-beta:
	required: true
	description: Release candidate version (beta, like 0.70.0)
	current-beta:
	required: true
	description: Current version (beta, like 0.69.1)

We also require the version to not start with v. We should add some validation to make the release workflow fail fast if the tags don't match the expected schema.

Relates to open-telemetry/opentelemetry-collector#7576, open-telemetry/opentelemetry-collector#7627