improve FOPCommandFormatsValidator / Prepare for phpstan

[SebSept]

I rewrote the class. It was a need while I was implementing the phpstan rule (#97). The basis still the same even if a lot of code has changed. The tests provided were a must to do this refactoring (gg @Kaudaj).

Features :

• Class can be used as a service (only a single public method)
• validate() has now 3 parameters instead of 4, domain(=namespace) and class name are replaced by Fully Qualified Class Name (no need to extract them before using the validator).
• Checks are explicit, inside methods, checkCommandNameIsConsistentWithClassName(), ...
• The regular expressions are now at class level, inside constants, COMMAND_REGEXP, ...
• validate() returns a ValidationResults class which embed all results (positive and negative) (class ValidateResult )

[SebSept]

Thanks for reviewing. That's right multi words domains are not handled. Your example is relevant. But currently, none exists and I'm used to don't code thing that are not needed. I think it's a better option to code things when they are needed not because we imagine they could exists. Our code must be ready to accept changes, but that's another question.

However, I'll give it a try tonight.

[SebSept]

I'll add some tests and we'll fix what's possible or not..

[SebSept]

Added tests with the current real data. Only one command is not correct (mine 😭 😄 )

Formats : ( domain and action are placeholders )

• class name : FOP\Console\Commands\Domain\DomainAction
• command : fop:domain:action
• service : fop.console.domain.action.command

Words separators :

• Command name : words separator : - (action words can also be separated by : (image generation commands).)
• Service name : words separator : _
• Class name : CamelCase separation

see ./Resources/commands-realworld.csv and Resources/commands-realworld.csv for examples.