Don't rely on internal MavenRepositorySystemUtils

Option 1: If you need a RepositorySystemSession, best seems to be creating a
MavenExecutionRequest, and then `container.lookup(DefaultRepositorySystemSessionFactory.class).newRepositorySession(mavenRequest)`. This is what's used both by Eclipse m2e and LemMinX-Maven

Option 2: see how
https://github.com/simpligility/maven-repository-tools/tree/master/maven-repository-provisioner
does it

No repository files or tests are named. Start by locating uses of the internal MavenRepositorySystemUtils and compare the MavenExecutionRequest plus DefaultRepositorySystemSessionFactory approach used by Eclipse m2e and LemMinX-Maven with the maven-repository-provisioner example. Done means the internal utility is no longer relied on and the resulting repository session behavior remains correct.

Escrita pelo modelo de indexação a partir do texto da issue.