NoSpacesAfterFunctionNameFixer - introduce fix_special_constructs option

[guilliamxavier]

Closes #4817
Opt-in version of #4837
Alternative to (but not incompatible with) #4893

(The first commits are just refactoring and optimization, the actual change is the last commit)

This option is enabled by default (to keep BC) but disabled in the @Symfony ruleset (cf. symfony/symfony#35588 (comment))

[guilliamxavier]

I probably should ask @nicolas-grekas what they think about the @Symfony ruleset part?

[nicolas-grekas]

In the Symfony CS, a space after echo is always desired (but no space after array).

[guilliamxavier]

Thanks. Well, with this PR, php-cs-fixer fix --rules=@Symfony would no longer remove spaces after echo (but would still remove them after array) 🙂 (To also have it add a space after echo (but not array) if there isn't one already, we would need #4435)

[kubawerlos]

The name fix_special_constructs is really confusing - why these 6 are "special" and other from $tokenKinds are not?

Can we have tokens option like in no_extra_blank_lines?

[guilliamxavier]

array, empty etc. are language constructs (dedicated tokens, cannot be called using variable functions) but require parentheses around their argument(s) (just like regular functions), whereas
echo, print etc. are "special" [language] constructs in that they don't expect parentheses around their argument(s) (like return or throw).
That's maybe confusing (and I could even add "why not clone?") but that's how the fixer was created (and see #1266) and my attempts to fix it so far have been blocked or ignored (at least that's how it feels like) 😕

Thanks for the review, I shall try to do like NoExtraBlankLinesFixer when I get more time...