Label release:merge-freeze should not block the release PR

[songy23]

See an example in #11904

[jade-guiton-dd]

CI run: https://github.com/open-telemetry/opentelemetry-collector/actions/runs/12358329691/job/34488568972

Hypothesis: This was a race condition where the check workflow started when the PR is created, but before the label was added, validating the if condition, but by the time the check actually ran, the label had been added. The workflow should have be rerun by the "labeled" event, but did not, because events caused by CI actions cannot trigger other CI actions.