Exclude single node deployments (capd/capm3) for rolling upgrade rules

What does this MR do and why?

When a MR was flagged with label ci-feature::test-rolling-upgrade the previous rules try to apply a cp_replica set to 3 for capm3 deployment (this could not works as they have only one node defined)

We can't apply the same exception selector (ENV_NAME) as we did for capd deployment as capm3 ENV can be either single node or HA

So I changed the rules to add an exception on CI_JOB_NAME patterns

will match all capd & capm3 deployments except the capm3-ha-xxxx

Gitlab rules doesn't support negative lookahead in regex so we can't use (?!ha) instead of [^h]

Related reference(s)

close #1236 (closed)

Test coverage

Edited by Loic Nicolle

Merge request reports

Loading