Cached container causes errors after TrashConfigSubscriber update

Problem/Motivation

During a recent deployment, we saw errors in the logs:

TypeError: Drupal\trash\EventSubscriber\TrashConfigSubscriber::__construct(): 
Argument #6 ($loggerFactory) must be of type Drupal\Core\Logger\LoggerChannelFactoryInterface, Drupal\Core\Action\ActionManager given

At first, we thought the problem was that Commit ed599e43 added a parameter to TrashConfigSubscriber but neglected to update trash.services.yml. Further analysis showed that autowiring should have handled that, so the problem is that the service container was not rebuilt during the deployment.

This may have been caused by a delay between updating the code and updating the database, but it can also happen when deploying with drush updatedb --no-cache-clear. I am not sure how common that is, but the option is there and some site owners will use it in order to avoid clearing caches unnecessarily.

This problem is temporary: as soon as the container is rebuilt, for whatever reason, it goes away. Fixing this issue should help anyone who uses that option and has not yet updated this module to 3.0.35+.

Steps to reproduce

1. Install Trash 3.0.29 on a Drupal 10.3+ site and enable it for at least one entity type (e.g. Content).
2. Update the code to 3.0.35:
   composer require drupal/trash:3.0.35
3. Run drush updatedb --no-cache-clear. It reports "No pending updates."
4. Visit the Trash settings page. It fails with an error from one of several classes whose constructors changed between 3.0.29 and 3.0.35, for example:
   ArgumentCountError: Too few arguments to function Drupal\trash\TrashEntityPurger::__construct(), 6 passed ... and exactly 7 expected
5. Alternatively, save trash.settings from the command line:
   drush cset trash.settings auto_purge.enabled 1 -y
   This fails in the config subscriber:
   TypeError: Drupal\trash\EventSubscriber\TrashConfigSubscriber::__construct(): Argument #6 ($loggerFactory) must be of type Drupal\Core\Logger\LoggerChannelFactoryInterface, Drupal\Core\Action\ActionManager given

Proposed resolution

1. Add a post-update function that rebuilds the service container. Testing shows that an empty post-update function does not trigger a rebuild with drush updatedb --no-cache-clear.
2. Remove explicit parameters from trash.services.yml to avoid confusion.
3. Pass a logger object instead of the logger factory, to follow Drupal standards.

Remaining tasks

User interface changes

None

API changes

The trash.config_subscriber service expects a logger object, not the logger factory.

Data model changes

None