Do not support core versions newer than current published beta or higher

Problem/Motivation

With Drupal 10 expected to be released in a couple weeks it would be ideal to have a tagged release, we have done the final parts of this work in #3289442: Automated Drupal 10 compatibility fixes where we marked s3fs dev branch as compatible with all D10 versions, present and future.

In #3323934: Breaking changes for public:// takeover in D10.1 from #1014086 we have discovered that, as of right now, s3fs will not be compatible with D10.1, and while the hope is this will be resolvable that has not yet been validated.

Due to some of our off-api library usage we also had issues in D9.3 with #3253414: Incompatibility with Drupal 9.3 where we were unable to prevent WSOD's on sites that upgraded.

Since we have not published the D10 tag we can prevent future issues now by only incrementing our version when we confirm compatibility with each release of Drupal Core. The downside of this is it will require dev effort several times a year to bump minor support (running under the assumption that a patch will not break us though that is not guaranteed). This is not helped by the fact we currently do not test public:// and private:// takeover thoroughly.

The alternative is we may end up breaking sites when D10.1 is released should we not have a solution to the known issues, and should any other issue occur in later D10..x releases we will not be able to prevent them either.

Steps to reproduce

Not Applicable.

Proposed resolution

Mark current dev as compatible only with D10.0, and increase the version only once a formal Drupal Beta is released and confirmed compatible.

Remaining tasks

Decision on path to take
Patch if necessary.

User interface changes

None

API changes

None

Data model changes

None