Bring new features from Symfony 3/4/5/6 into our container

Since we're adding interface aliases to core modules, would it make sense to start doing the same for contrib modules?

To extend this question:

I see for now, in core, we are keeping the string service ids, and are only adding interface names as aliases.
For existing services this makes sense, because changing the existing service name would break BC.

In symfony, it is possible to use a class name instead of a custom service id.
This even seems to be the standard now, according to https://symfony.com/doc/current/service_container.html#creating-configur....

Automatic Service Loading in services.yaml

The documentation assumes you're using the following service configuration, which is the default config for a new project:

So the question is, should we adopt or allow using class names as service names in our conventions for contrib and for new services in core, or should we stick to custom string ids?

Beyond autowiring, we have a small issue in the URL generator not respecting the Unicode property of route regexps 🐛 Support Unicode regular expressions in routes, from Symfony 4.3 Active .