[MRESOLVER-310] Preserve configuration of Enhanced LRM in local repo

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

We can configure  `Enhanced LRM` with options like `Split Local Repository` which change local repo layout.

Eg.
- local repo is created by main Maven process and I want to use this repo as is or with CLRM with IT test, IT tests have sanboxes environment with own Maven settings ... so artifacts in `outer` / `tail` repo will be not found because layout of local repo is wrong interpreted.

Next case
- when we change configuration on LRM, new paths will be used and old items will remains in forgotten locations

Proposition:
- create and store LRM configuration in repo and when configuration exist use is as primary
- when current session has a configuration which is different from stored in repo inform user by warn that should simply remove/clean repo to take new configuration on place.

---

**Issue Links:**
- [MRESOLVER-163](https://issues.apache.org/jira/browse/MRESOLVER-163) Introduce "configuration" or "feature" helper to centralize various flags/params/configs

**Remote Links:**
- [GitHub Pull Request #248
](https://github.com/apache/maven-resolver/pull/248)

Start by reading the Enhanced LRM discussion and the related MRESOLVER-163 issue, then inspect GitHub pull request #248 for prior work. Done means the LRM configuration is stored and reused from the local repository, and a differing session configuration produces the proposed warning.

Written by the indexing model from the issue text.