Use resource filtering for mng-12534 IT plugin mavenVersion

Move the plugin POM to src/test/resources-filtered/ (which already
has <filtering>true</filtering> in the core-it-suite build) and
replace the hardcoded version with ${maven-version}, defined in the
ITs parent POM.

Maven resource filtering resolves the token at build time, so the
version always matches the Maven build under test — including during
the release process, where the release plugin bumps the version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: gnodet

…ng-12534-after-annotation/plugin/pom.xml …ng-12534-after-annotation/plugin/pom.xmlits/core-it-suite/src/test/resources/mng-12534-after-annotation/plugin/pom.xml renamed to its/core-it-suite/src/test/resources-filtered/mng-12534-after-annotation/plugin/pom.xml its/core-it-suite/src/test/resources/mng-12534-after-annotation/plugin/pom.xml renamed to its/core-it-suite/src/test/resources-filtered/mng-12534-after-annotation/plugin/pom.xml

@@ -11,7 +11,7 @@
 
   <properties>
     <javaVersion>17</javaVersion>
-    <mavenVersion>4.0.0-rc-6</mavenVersion>
+    <mavenVersion>${maven-version}</mavenVersion>
   </properties>
 
   <dependencies>