adapt pipeline for prod releases

[dragonchaser]

This PR splits the check_version pipeline into two steps, the step for detecting leftover %%NEXT_PRODUCTION_VERSION%% placeholders only is run when the label production_release is set for the PR.

/cc @ScharfViktor && @individual-it

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dragonchaser]

Please merge as is, this will never get green because of set test labels.

[ScharfViktor]

Please merge as is, this will never get green because of set test labels.

we can't merge it until getting greenall-checks-finished

[ScharfViktor]

I see your last running

to get green you need run CI without 🎉 Release in the title and label production_release
try to force push

[dragonchaser]

@ScharfViktor I did, otherwise I would not be able to test the functionality.

[individual-it]

This does not work, because If at least one of the conditions in the when block evaluate to true the step is executed, otherwise it is skipped. see: https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution

Also, the linter shows a warning:

A condition is evaluated to true if all sub-conditions are true.

Suggested change

	event["pull_request"],
	{
	"evaluate": 'CI_COMMIT_PULL_REQUEST_LABELS contains "production_release"',
	},
	{
	"event": "pull_request",
	"evaluate": 'CI_COMMIT_PULL_REQUEST_LABELS contains "production_release"',
	}

or

Suggested change

	event["pull_request"],
	{
	"evaluate": 'CI_COMMIT_PULL_REQUEST_LABELS contains "production_release"',
	},
	{
	"evaluate": CI_PIPELINE_EVENT == "pull_request" && CI_COMMIT_PULL_REQUEST_LABELS contains "production_release"',
	},