Use new 11.4 dev-pipeline

[ivy-rew]

Update pipelines to v3 which are aware of the capabilities of 11.4: This change should serve as sample how to update other market-artifacts to comply with the ivy-core:11.4

• introduces a property to steer the project.build.plugin.version and tester.version
• adds snapshot repositories to the POM's in order to consume SNAPSHOT artifacts during dev-pipeline runs
• upgrade the versions to the latest available from 10.X using the maven cli command line:
• mvn --batch-mode versions:set-property versions:commit -Dproperty=project.build.plugin.version -DnewVersion=10.0.16 -DallowSnapshots=true
• mvn --batch-mode versions:set-property versions:commit -Dproperty=tester.version -DnewVersion=10.0.16 -DallowSnapshots=true

for traceability I'd love to see this taken as receipt, also in terms of its history. each change is an own commit. manual and automated changes come separate.

• if you need to build a hack to comply with 11.4, please isolate it in a distinct commit, and create an issue for it, just like I did it by example on The APIkey variable is defined in an invalid format #32 . You can than plan to actually introduce distinct versions targeting leading-edge releases, to get rid of such technical depts. Ask @ivy-sgi to plan these efforts.

This reverts commit 53242e2.

[github-actions]

Test Results

3 tests  ±0   0 ✅ ±0   5s ⏱️ -2s
1 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌  - 3   3 🔥 +3 

For more details on these errors, see this check.

Results for commit 8cafd1b. ± Comparison against base commit 846d01a.

♻️ This comment has been updated with latest results.

[ivy-rew]

the build still fails as @ivy-sgi already found out, this is due the invalid URI in use which is reported as #28.
it's good to get feedback on this problem, though we should maintain a mock-server, just like for every other soap/rest connector., so we can test without running into infrastructure problem with the third-party.

[phhung-axonivy]

These changes look good.
Should I merge it?