Reinstate nearest functionality

[dareni]

As of junit-platform-console-standalone version 1.10.1 invocation with method option '-m' is correct.

[dareni]

The 'Run Nearest Test' and 'Debug Nearest Test' options do operate as
expected, and run/debug all the tests in a class instead of just the
nearest. This change was a work around introduced because of a bug in
a prior version of junit-platform-console-standalone.

As of junit-platform-console-standalone version 1.10.1, invocation with
method option '-m' is correct so this patch once again reinstates the
'nearest' functionality.

[rcasia]

Hi @dareni,

This still has problems when we have tests with parameters like this:

    @ParameterizedTest
    @CsvSource({
            "1, 2",
            "2, 4",
            "3, 6"
    })
    void testWithParameters(int input, int expected) {
        assertThat(input * 2).isEqualTo(expected);
    }

When a test method has parameters, we are required to select testWithParameters(int, int) instead of testWithParameters.

I am checking whether I can add a the required canonical name on Tree creation from positions_discoverer.lua.