Support all types of version constraints in core_version_requirement for NEXT_MAJOR run

Issue information

From user: acbramley

Related to !226 (merged)

Contribution record

Fork management

Problem/Motivation

I started working on a module to replace some deploystacks matrix logic with the new NEXT_MINOR and NEXT_MAJOR work in #3456091: Fix gitlab CI setup to run tests on next major/minor. For some reason the NEXT_MAJOR run wasn't running any tests.

I tracked this down to how the grep/sed works on the .info.yml file.

The module had core_version_requirement: '>=10.3' which did not get parsed correctly by the grep or sed resulting in no tests being run https://git.drupalcode.org/issue/scheduled_transitions-3456091/-/jobs/1915450

This was not the case for the NEXT_MINOR (because I guess it already supported 10.3)

Steps to reproduce

Use a constraint that isn't ^10 in .info.yml and doesn't include ^11

Proposed resolution

Fix the grep/sed to account for all variations of version constraint, OR just completely replace it with core_version_requriement: ^11 - why do we need to shim anything into the existing constraint?

Remaining tasks

Agree
Do it