Remove requirement for core_version_requirement for module to be compatible with Drupal 9

To prevent future contrib module upgrade bottle necks going from D9>D10, D10>D11, etc. yet setting some limits, perhaps recommending defining a minimum and maximum version could be considered? That way contrib modules can be easily installed and worked on in the next official major release while it's underway, but not yet released.

Maybe something like @japerry suggested in Navigating core_version_requirement?

What should core_version_requirement look like?

My personal preference is to work with the next ‘beta’ of a major version. That allows developers to immediately work with a module, but doesn’t allow it to automatically work with the next stable release:
[...]
If your module supports Drupal 9 and 10:
core_version_requirement: >=9.2 <11.0.0-stable

This is also the proposed solution in 📌 Add a composer plugin that supports 'composer require-lenient' to support major version transitions Active , though that issue only suggests setting a minimum.

Updated the issue summary: The core attribute is already deprecated, and has been ignored since Drupal 8.
Fixed formatting and a typo.

Fixed more formatting in issue summary.

If the proposed resolution is let a maintainer remove the core_version_requirement setting in from ".info.yml", and thereby making the project core version agnostic.

The proposed resolution is equivalent to what the maintainer will get if they use the following unbounded version constraint:

core_version_requirement: >=8.0

I.e.: There is not need to change core to have this behaviour.

Using an unbounded version constraint is one of the possible resolutions under discussion in 📌 Add a composer plugin that supports 'composer require-lenient' to support major version transitions Active .

I think this issue should be closed as a duplicate.