It still requires a deprecation in case you do not provide the name parser in the constructor, right? (it should not be mandatory for BC reasons).

Indeed, it should not be mandatory. I updated this to make it optional, instantiating the base name parser directly if not injected. I think it's fine to not deprecate here.

Should be done in 3.4, right?

It intends to fix my comment in #23371 PR description:

However, the original fix prevents using the proper name parser in case it was replaced

So the target is right. However, it still "breaks" if the command is instantiated elsewhere (but it's unlikely to happen). That's why I'd expect to get at least a deprecation in case the parser isn't injected in the constructor.

As a side note: In 3.4, we could even use a service locator, or leverage on #22734 to keep dependencies lazy and get rid of the ContainerAwareCommand.

Adding a deprecation in 3.2 is a no-go.
This is a BC break, so cannot be done in 3.2.

Then I think #23371 should be merged.
Closing here.