Performance/TaxonomyMetaInOptions: various improvements

[jrfnl]

Performance/TaxonomyMetaInOptions: extend AbstractFunctionParameterSniff

As things were, the determination of whether or not a T_STRING is a call to any of the global WP options functions, was severely flawed.

By switching the sniff over to be based on the WordPressCS AbstractFunctionParameterSniff class, this flaw is mitigated.

Includes adding a slew of additional tests, some of which (line 8 - 13, line 50, 51) are specific to the flaw being addressed in this commit.

Additionally, the tests have been made more comprehensive and varied by:

• Testing against false positives for calls to methods or namespaced function calls (= the issue being addressed in this PR).
• Ensure function import use statements are not flagged. We're not interested in those.
• Safeguarding that function calls using PHP 5.6+ argument unpacking are not flagged.
• Safeguarding handling of PHP 8.0+ attribute class using the same name as a target function.
• Safeguarding that the functions are not flagged when used as a PHP 8.1+ first class callable.
• Adding tests with more variations:
  • Non-lowercase function call(s).
  • Fully qualified function calls.
  • Use PHP 7.3+ trailing comma's in a few function calls.
  • Comments in unexpected places.

Performance/TaxonomyMetaInOptions: add support for handling PHP 8.0+ function calls using named parameters

Includes tests.

Performance/TaxonomyMetaInOptions: add support for handling PHP 8.0+ nullsafe object operator

Includes test.