Remove unactionable warnings when a plugin is ignored by m2e

[vtintillier]

Discussed in #1229

Especially @kwin and @laeubi agreed on this proposal to avoid those useless warnings:

I think the message part inside the ignore lets m2e emit that warning. I don't think this warning is useful but rather confusing therefore I propose to remove all message lines from

m2e-core/org.eclipse.m2e.core/lifecycle-mapping-metadata.xml

Line 131 in e379405

<message>maven-enforcer-plugin (goal "enforce") is ignored by m2e.</message>

^{Originally posted by vtintillier February 2, 2023}
Hello,

I am not sure if the behavior I see is intended or not.

maven-enforcer-plugin removed their META-INF/m2e/lifecycle-mapping-metadata.xml file in their last 3.2.1 release (apache/maven-enforcer#192). As a result, we see this warning in all our poms:

maven-enforcer-plugin (goal "enforce") is ignored by m2e

It seems this messages originate from this code:

m2e-core/org.eclipse.m2e.core/lifecycle-mapping-metadata.xml

Lines 120 to 134 in e379405

	<pluginExecution>
	<pluginExecutionFilter>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-enforcer-plugin</artifactId>
	<goals>
	<goal>enforce</goal>
	</goals>
	<versionRange>[1.0-alpha-1,)</versionRange>
	</pluginExecutionFilter>
	<action>
	<ignore>
	<message>maven-enforcer-plugin (goal "enforce") is ignored by m2e.</message>
	</ignore>
	</action>
	</pluginExecution>

So my question is: is this expected that goals ignored in m2e-core own lifecycle-mapping-metadata.xml appear as warnings in the editor, whereas goals ignored in maven plugins own lifecycle-mapping-metadata.xml do not?
Also is there a way to disable those warnings?

Thanks
Vivien