… being an array

This adds support to the `function-component-definition`  rule to have the `namedComponents` rule be an array.

…methods`: use report/messages convention

Test detection of Class Components and Stateless Function Components
Lay scaffolding for other flavors of tests including further component types, pragma detection, and utils functions

The default React import and named React import specifiers are tracked during a Components.detect rules definition.
Rules using Components.detect can access the default import specifier using `components.getDefaultReactImport()` and an array any named import specifiers using `components.getNamedReactImports()`
Within a rule, these specifier nodes can be checked to ensure identifiers in scope correspond with the imported identifiers.

Not treating this as semver-minor since it's not part of the documented API.

parsers.all generates an extraComment which is appended to test case examples and their expected output.
Eslint's suggestions API also allows recommended code changes, and RuleTester compares expected changes against generated changes. However, parsers.all didn't augment these expected outputs with the extraComment.

Rename Components test suite filename to match sibling lib/util/Components filename.
Extend Components testComponentsDetect function to accept custom instructions, and to accumulate the results of processing those instructions.
Add utility to check whether a CallExpression is a React hook call.

…r ternary