[MNG-8660] Decouple legacy prompter from implementation details

[oehme]

JIRA issue: MNG-8660

The legacy prompter should only use the Prompter interface, not the DefaultPrompter implementaiton, so that the Maven daemon can override how prompting is implemented.

See apache/maven-mvnd#1303

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

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MNG-XXX] SUMMARY,
  where you replace MNG-XXX and SUMMARY with the appropriate JIRA issue.
• Also format the first line of the commit message like [MNG-XXX] SUMMARY.
  Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean 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.

[oehme]

@gnodet this is one possible solution. The other would be to implement both the new and the legacy interfaces in the Maven daemon.

[gnodet]

@oehme LGTM. Does that actually fixes the mvnd ITs ? I am slightly worried about a possible visibility issue for the beans.

[oehme]

Yep, when I build this branch locally and then upgrade the Daemon to it, the tests pass.

Should I create a jira issue for this?

[jira-importer]

Resolve #9357