Notify downstream users that ContainerAware is going away

The MR will fail for the uses in core that haven't been removed, we should explicitly add these (for now) instead of the wildcards.

The outcome here will also determine what we do with ClassResolver::getInstanceFromDefinition():

    if ($instance instanceof ContainerAwareInterface) {
      $instance->setContainer($this->container);
    }

If we decide that ContainerAware should go away in Drupal 11 I think we should trigger a deprecation from there to further notify existing users?

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Resolved the conflicts.

We can safely remove the ResetInterface skip here as that has already been resolved in 11.x (although this means we probably need two branches here as we will have to apply these changes to 10.3.x as well).

Given that Symfony is no longer supporting this interface our choice is to remove it entirely or clone it and implement it ourselves. There are some uses in contrib according to http://grep.xnddx.ru/search?text=ContainerAwareInterface but on inspection all sample cases look like they should be able to use dependency injection instead.

Therefore I think we should also deprecate that part of ClassResolver here, updated the IS and added a sample deprecation to core to see what breaks.

Added a change record and deprecation and adjusted the existing test coverage.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Rebased to prove that review-bot was wrong, which it was.
Also RTBCed.

Committed ab80fb2 and pushed to 11.x. Thanks!
Committed 96664ce and pushed to 10.3.x. Thanks!

I resolved conflicts in core/.deprecation-ignore.txt ... fingers-crossed I did it right :)

I had to add a follow-up commit on 10.3.x due to the deprecation being triggered by our tests - see https://git.drupalcode.org/project/drupal/-/commit/aafa15549cd89625ef6ce...

Automatically closed - issue fixed for 2 weeks with no activity.