Configurable Java and Maven version, using 21+3.9 for dev

[ivy-rew]

make Java and Maven version configurable, so that we can consume newer versions on the LE 11.4 dev-pipeline.

[ivy-rew]

alternative approach for #25

[phhung-axonivy]

Hi @ivy-rew
Should we change the ci.yml uses with a new tag name? e.g. v3?
When we merge it into the master branch, do we run git tag commands manually or have a job to do the tagged task?

[ivy-rew]

you can decide on this, though I'd suggest to keep the 'v2' tag for now, as I think there is no functional/breaking change in it and we we can 'spare' the roll-out effort to update all the consumers to the new version.

Once the thing is on the master branch you can tag it, either using the github-ui or with git commands in your terminal. There is no automated job for this.

[ivy-rew]

Will you take the lead on merging this and tagging it @phhung-axonivy ? Or shall I apply it?
Or do we have further need for discussion?

[phhung-axonivy]

You introduced two new inputs in the ci.yml file, and you used them in the dev.yml file.
With ci.yml@v2, these inputs have not been introduced yet. That's the reason why I ask you to use a new tag v3.
If it's not taking too much of your time, please apply it.

[ivy-rew]

Ok I'll introduce it and consume it by example in msgraph and a-trust ... so you can use this as copy example how to proceed in the future

[phhung-axonivy]

Thank you so much @ivy-rew

[ivy-rew]

v3 is introduced: the adaption can be copied from here ... I think you can share this way to go with the team and apply it to all artifacts in the market.

• a-trust: Use new 11.4 dev-pipeline a-trust-connector#30
• ms-graph: upgrade to dev@v3: use java21+maven3.9+project-build-plugin:11.4 msgraph-connector#101