Consequently, the constructor method can be removed in Symfony 8.0.

this is not true. Removing the parent constructor would require firstdeprecating calling it (even without a name), so that the code is ready for the removal. And making the parent constructor call mandatory in 6.4 LTS and deprecated in 7.3 would make it harder for the ecosystem to support both versions at once (which might encourage them to drop support for our LTS version before its EOL, which is bad for our communication about the LTS).
The cost of keeping an empty constructor method is null here, so we should give more time to the ecosystem (deprecating calling it in 8.1 for removal in 9.0, allowing to support 7.4 LTS and 8.x with the same code not calling it).

However, I'm not sure encouraging to not call the parent constructor is the right solution.

Damn!@stof you're right, I removed that sentence from the PR description. It's hard to deprecate since there is no way to know if the constructor was either called or there is no construct at all in the subclass. Let's revert that part, thanks!

Update! removed deprecation about passing the command name through the constructor. However, we can update the documentation to remove theparent::__construct() call from all commands.

I'll split this PR into two, so we can discuss both topics separately

moving the deprecation to a separate PR:#59565, and closing the other proposal for now, as it doesn't seem worthwhile at this point