Prepare release script sed usage is still fragile

[mx-psi]

Component(s)

No response

Describe the issue you're reporting

For releases we use the "Automation - Prepare Release" workflow, which uses this script to create a PR that is the first step of the contrib release.

It used to look like

opentelemetry-collector-contrib/.github/workflows/scripts/release-prepare-release.sh

Lines 33 to 34 in fbd85e0

	sed -i.bak "s/${CURRENT_BETA}/${CANDIDATE_BETA}/g" ./cmd/oteltestbedcol/builder-config.yaml
	sed -i.bak "s/${CURRENT_BETA}/${CANDIDATE_BETA}/g" ./cmd/otelcontribcol/builder-config.yaml

and after #23977 it looks like

opentelemetry-collector-contrib/.github/workflows/scripts/release-prepare-release.sh

Lines 33 to 36 in 401c353

	sed -i.bak "s/v${CURRENT_BETA}/v${CANDIDATE_BETA}/g" ./cmd/oteltestbedcol/builder-config.yaml
	sed -i.bak "s/v${CURRENT_BETA}/v${CANDIDATE_BETA}/g" ./cmd/otelcontribcol/builder-config.yaml
	sed -i.bak "s/${CURRENT_BETA}-dev/${CANDIDATE_BETA}-dev/g" ./cmd/otelcontribcol/builder-config.yaml
	sed -i.bak "s/${CURRENT_BETA}-dev/${CANDIDATE_BETA}-dev/g" ./cmd/oteltestbedcol/builder-config.yaml

This sed command may replace versions from dependencies we are replacing, which was the motivation for #23977. The current version still has some issues:

1. The . on a version like 0.80.0 are still interpreted as 'any character' by sed, which is not what we want. A way to solve this is to do ${CURRENT_BETA//\./\\.} to escape dots as pointed out by @astencel-sumo
2. Even when solving (1), we still can run into issues if a dependency in the manifest were to exactly match the version used by the Collector (not something that can happen today with the current set of replaces).

We should rework how we handle this replacement to avoid issues in the future.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.