Set up locator services to fix NPE during Maven priming

[sdedic]

Maven module attempts to find the included Maven libraries using InstalledFilesLocator which wasn't found, so maven home == null causing NPEs and broken classpath.

The testsuite might work occasionally, as if the Artifact tests, which contain this setup already, or other test that downloads Micronaut libraries to local repository runs BEFORE the completion tests, Maven priming is skipped as all necessary poms are available and the project loads smoothly. If the tests are ordered "incorrectly", maven priming fails and fail the completion tests.

I have moved the setup to a common test base.

@mbien this is the cause of failing tests i https://github.com/apache/netbeans/actions/runs/8444656505/job/23130853755#step:6:1262

[mbien]

@sdedic thanks for looking into this. I vaguely remember that something similar happened before when either the micronaut or gradle tests were throwing exceptions while still passing and we only noticed it since we tried to debug something else.

I believe I saw somewhere a setting for the test suite to fail tests if it sees an exception (or maybe a certain log level?) in the log, do you think this would make sense here?

[sdedic]

do you think this would make sense here?

It could make sense in more places. But need to be applied very carefully. There are number of "harmless exceptions" from the module system etc, which are now present in the logs. It would be best to work for a while on testing infrastructure to improve suite setups to remove them, of course.