[MNG-7883] Also print groupId and version in the Reactor Build Order

[chenchc6]

JIRA Issue: MNG-7883

Description:
This pull request addresses the enhancement described in JIRA issue MNG-7883. The goal is to improve the readability and completeness of the Reactor Build Order output by including groupId and version information for each module. This change is necessary to provide developers with more detailed information about the modules being built, which can help in debugging and understanding the build process.

Changes Made:

• Modified the ExecutionEventLogger class to include groupId and version information in the Reactor Build Order output.
• Updated the sessionStarted method to format the output with the new information, ensuring clarity and consistency.

Implementation Details:

• The sessionStarted method in ExecutionEventLogger was updated to construct a formatted string containing the groupId, artifactId, and version for each module.
• Adjusted the spacing and alignment to ensure the output remains clear and readable.

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.

[gnodet]

I would make the behaviour configurable using a user property (added to https://github.com/apache/maven/blob/master/api/maven-api-core/src/main/java/org/apache/maven/api/Constants.java)