[MSHARED-1074] Improvement performance of getMavenVersion in ForkedLauncher

**[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** opened **[MSHARED-1074](https://issues.apache.org/jira/browse/MSHARED-1074?redirect=false)** and commented

In method `getMavenVersion` in ForkedLauncher new Maven process is forked every time.

We can cache output by Maven home or try to read from properties files in Maven home `/lib/maven-core-xxx.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties`

There is also possibility to use Maven wrapper for executing - in this case we can read version form maven-wrapper.properties

---

**Issue Links:**
- [MSHARED-1140](https://issues.apache.org/jira/browse/MSHARED-1140) Simplify Maven version extraction in the forked launcher

Start in ForkedLauncher at getMavenVersion and review how the Maven process is forked on each call. Compare the issue's proposed Maven-home cache, maven-core pom.properties path, and maven-wrapper.properties approach, then check the linked MSHARED-1140 issue for the intended direction; done means Maven version extraction avoids unnecessary process launches without breaking wrapper handling.

Written by the indexing model from the issue text.