[MNG-7806] Plugins verification - remove used in module(s) report

[slawekjaranowski]

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.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MNG-XXX] SUMMARY,
  where you replace MNG-XXX and SUMMARY with the appropriate JIRA issue.
• Also format the first line of the commit message like [MNG-XXX] SUMMARY.
  Best practice is to use the JIRA issue title in both 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 Core IT successfully.

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.

[cstamas]

LGTM, but today I'd maybe completely remove "used" thing. First, usually plugin is defined in parent and most usually is inherited by all child modules, and I agree, it is just a mess. IMHO, it is more important where plugin is defined (to make user go there and edit the POM)

[slawekjaranowski]

LGTM, but today I'd maybe completely remove "used" thing. First, usually plugin is defined in parent and most usually is inherited by all child modules, and I agree, it is just a mess. IMHO, it is more important where plugin is defined (to make user go there and edit the POM)

Agree - so I will remove it at all.

[cstamas]

Note: forward port to Maven4/master required, as currently validation is 1:1 in both (maven-3.9.x and master), JIRA adjusted as well.