ops: using cache and 3.9.5 version about maven on workflow

[manuraf]

List of Changes

1. Implemented the use of the s4u/setup-maven-action action in the GitHub workflows.
2. Set the Maven version to 3.9.5.
3. Enabled Maven cache to reduce the execution time of the workflows significantly.
4. Fix onboarding-ms unit test

Motivation and Context

The entire repository is set up to perform builds using Maven with version 3.9.x. In the current GitHub workflows, using the setup-java action alone results in the use of an older version of Maven. This change is required to ensure that the workflows use the correct Maven version (3.9.x), aligning with the repository's setup. Additionally, the use of Maven cache is crucial for significantly reducing the execution time of the workflows by caching the Java libraries.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication