…esLoader final (xabbuh)This PR was merged into the 7.4 branch.Discussion----------[Routing] make RoutingControllerPass and AttributeServicesLoader final| Q             | A| ------------- | ---| Branch?       | 7.4| Bug fix?      | no| New feature?  | no| Deprecations? | no| Issues        | see#61492 (comment)| License       | MITCommits-------9986139 make RoutingControllerPass and AttributeServicesLoader final

… of known DI tags (xabbuh)This PR was merged into the 7.4 branch.Discussion----------[DependencyInjection] add routing.controller to the list of known DI tags| Q             | A| ------------- | ---| Branch?       | 7.4| Bug fix?      | no| New feature?  | no| Deprecations? | no| Issues        || License       | MITre-reading#61492 I wonder if we don't have to add the new tag to this listCommits-------593ee8f add routing.controller to the list of known DI tags

…ler services (nicolas-grekas)This PR was merged into the 7.4 branch.Discussion----------[Routing] Simplify importing routes defined on controller services| Q             | A| ------------- | ---| Branch?       | 7.4| Bug fix?      | no| New feature?  | no| Deprecations? | no| Issues        | -| License       | MITFine-tuning#61492Before:```yamlcontrollers:    resource: attributes    type: tagged_services```After:```yamlcontrollers:    resource: routing.controllers```And when using `MicroKernelTrait` (the default recipe), there's nothing to configure to have routes loaded from `#[Route]` attributes:```yaml#config/routes.yaml# the file can be just empty from any config, and only have a comment saying what it's for``````php// config/routes.phpreturn Routes::config([]);```The way to opt-out from this `routing.controllers` import would be to override the `Kernel::configureRoutes()` method.Commits-------13e25ca [Routing] Simplify importing routes defined on controller services