Create 3.3.x release for Drupal 10

Current patch on #3285981: Automated Drupal 10 compatibility fixes still supports Drupal 8 (^8.8.0). With the changes coming from #3256597: Replace deprecated library core/jquery.once with core/once per D.O. Issue #3158256 the minimum supported version will be 9.2.0 (when core/once has been created).

I'm confident there are no Drupal 8 installations around, but just to be safe I'd say the core minimum version should be updated accordingly if #3256597: Replace deprecated library core/jquery.once with core/once per D.O. Issue #3158256 lands first.

Although the general understanding in #3256597: Replace deprecated library core/jquery.once with core/once per D.O. Issue #3158256 is a major version bump is not needed.
Neither is needed for D10 compatibility. So this issue should not block the other two.

@gambry Not sure where you get the idea that there are no Drupal 8 installations around, when there are still at least 119K of them , about half of the total number of D9 sites. Drupal 8 has about 14% of all Drupal installs, to D9's 30% of the total: https://www.drupal.org/project/usage/drupal

Changing status, as there's nothing needing work here.

Not sure where you get the idea that there are no Drupal 8 installations around, when there are still at least 119K of them

I was being sarcastic @jcnventura, since it has been EOL for one year now.
I should have put a "😉".

Not sure why 3.2.1 is not marked as D10-compatible, while 3.1.1 is, but this seems to be the best issue match for that problem. Do we really want to block 3.2.x for D10 and force 4.x, while retaining 3.1.x for D10 too ?

D10 support in 3.1.1 was a mistake that if it was possible to revert should be. The decision on whether 3.x or 4.x will be the D10 version is a
bit left to the maintainers.

Pros and cons for 4.x being the D10 version:
Pros: Allowing the thousands of D8 sites to be have a supported version that is not forever 3.2.2, 3.2.3, 3.2.4, etc, etc. (and having to manage a 3.2.x branch)
Cons: Anyone on Drupal 10 doing "composer require drupal/admin_toolbar:^3" will get 3.1.1 installed.

As of berdir comment https://www.drupal.org/project/admin_toolbar/issues/3256597#comment-1475... I think that we will go for a 3.3.x branch for D9-D10 compatibility. The 3.2.X branch could receive security release.

OK. That's a good choice.. Please note that in git repo terms, you don't have to create a 3.3.x branch, but one of these days you might need to create a 3.2.x branch, if it ever becomes aparent that you need to apply a security patch to whatever is the latest 3.2.x tag.

However, creating that branch can be postponed for later, and easily done by:

git checkout 3.2.1 (or whatever is the last 3.2.x tag)
git checkout -b 3.2.x
git push -u origin 3.2.x

3.3.0 is out, so this can now be closed.