Do not override container services at runtime

Problem/Motivation

Followup from #3583505: Use Symfony PhpDumper instead of a serialized array container structure

Drupal containers are not completely frozen; we override Symfony's Container::set() because we make some changes at runtime:

  public function set(string $id, ?object $service): void {
    // Symfony prevents replacing already-initialized services. Drupal allows
    // this; ModuleInstaller swaps the route provider during module install.
    unset($this->services[$id]);
    parent::set($id, $service);
  }

Steps to reproduce

Proposed resolution

Find out all places that we do this
Figure out a better way
Remove this override

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet