[MSHARED-1035] Get rid of maven-plugin-testing-tools for IT test

[slawekjaranowski]

IT tests will be executed by maven-invoker-plugin

---

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes. Also be sure having selected the correct component.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MSHARED-XXX] - Fixes bug in ApproximateQuantiles,
  where you replace MSHARED-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[michael-o]

That's massive..., will run...

[slawekjaranowski]

Idea and way how to was done:

• add simple maven plugin src/it/setup-mock-plugin/src/main/java/it/test/MockAnalyzeMojo.java
• build and instal plugin in setup job of m-invoker-p
• plugin generate target/analysis.txt with result of executing
• use plugin in each IT test
• assert content of target/analysis.txt in verify.groovy

[slawekjaranowski]

I can't use new version of maven-plugin-testing-harness ... because for tests MavenProject instance is needed ...
MavenProject must contains resolve all dependency which is difficult to mock

[michael-o]

Tests pass!

[slawekjaranowski]

All test pass ... on GH and Jenkins
even with 18-ea on localhost 😸