Allow to override extension by introducing plugin weights / priorities

Thanks, approach makes sense. Can you add an automated test case?

We should also sort by priority in \Drupal\graphql\Plugin\SchemaExtensionPluginManager::getExtensions() which is used by non-configurable schema plugins.

Added test.

Alright, added to the merge train! Thanks!

There is a deprecation incompatibility with 🐛 Cache collision when multiple servers are using the same schema plugin Active , opened a follow-up merge request.

IMHO, we should presave extensions keys.
It is useful information and can be used in the AlterableComposableSchema.
Opened issue https://www.drupal.org/project/graphql/issues/3515245 🐛 Sort extensions by priority and presave extension key. Active