MNG-11875 replace org.fusesource.jansi:jansi with org.jline:jansi

[KevinSailema]

This pull request addresses issue #11875 by replacing the dependency org.fusesource.jansi:jansi with org.jline:jansi in the Maven 3.10.x line.

Validation performed

• Focused tests for CLI and logging paths:
  • mvn -B -pl maven-embedder,maven-slf4j-provider -am -DskipITs -Drat.skip=true -Dtest=MavenCliTest,MavenSimpleLoggerTest -Dsurefire.failIfNoSpecifiedTests=false test
• Distribution packaging path:
  • mvn -B -V -pl apache-maven -am -DskipTests -DskipITs -Drat.skip=true package
• Both commands completed successfully in this branch.

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
• Run mvn verify to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.
• You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[slawekjaranowski]

@KevinSailema please look for my change:

• Migrate from JAnsi to JLine, introduce MessageBuilderFactory #11874

In master branch we already ues jline, so your change should be targeted to branch maven-3.10.x

[KevinSailema]

Thanks for the guidance. I have retargeted this PR to maven-3.10.x and kept the change minimal for #11875 (single commit, 4 files). Also aligned with the migration direction discussed in #11874.

[slawekjaranowski]

I'm not sure if it will working .... we still use shared-utils with old dependencies
Please push a simple commit .... CI on github was not triggered

[KevinSailema]

I pushed an additional commit (797bcbe) to trigger CI as requested.

[slawekjaranowski]

Ok, build pass on CI ...

I build locally and .... when use it all colors are disappeared

[KevinSailema]

I reproduced the local color regression and pushed a fix in fbab46f (compatibility bridge for org.fusesource.jansi over org.jline:jansi).

Validation performed:

• mvn -B -pl maven-core,maven-embedder,maven-slf4j-provider -am -DskipITs -Drat.skip=true -Dtest=MavenCliTest,MavenSimpleLoggerTest -Dsurefire.failIfNoSpecifiedTests=false test
• mvn -B -V -pl apache-maven -am -DskipTests -DskipITs -Drat.skip=true package
• Local TTY verification: ANSI colors are present for default and style.color=always, and disabled for batch mode and style.color=never."

[slawekjaranowski]

@KevinSailema thanks for your engagement, I have merged my PR - #11874
where I did some more tasks, like remove maven-shared-utils, change path for native library and so on ...

by the way - invite to next contributions