ConsoleLauncher: warn when using --select-class with a class that is not accepted by the --include-classname rules

[fredlund]

When using the ConsoleLauncher to execute tests in a class FirstTesterMon.java, selected by the option --select-class, no tests were found. This is correct, as I had not specified any --include-classname nonstandard rule.

However, it would have been really helpful to get a warning message in the style of:
WARNING: you have specified to scan a class FirstTesterMon; however this class will NOT be scanned due to the rules for classname scanning. Consider specifying a --include-classname rule.

Or alternatively, and perhaps more sane: if a class is specified using --select-class always scan it even if the name does not match the --include-classname rules.

[sormuras]

Related to #733:

[...] that --select-method should by-pass the --include-classname is valid. Same goes to classes passed via --select-class. Both should be included, even if the active "include pattern" does not match.

[sbrannen]

Tentatively slated for 5.7 M2 solely for the purpose of team discussion

[marcphilipp]

Team decision: Add explicitly selected classes from --select-class and --select-method to the include patterns passed when constructing the ClassNameFilter so that these would always be executed regardless of the implicit or explicit class name filter.