KOGITO-7703 Quarkus nightlies: Use integration branch

[radtriste]

Tests to be done

TODO:

• [ ] How to update to latest released version of a quarkus branch once we branch the integration branch ?
• [ ] Jenkins PR checks on integration branch

Many thanks for submitting your Pull Request :heart:!

Please make sure that your PR meets the following requirements:

• [ ] You have read the contributors guide
• [ ] Your code is properly formatted according to this configuration
• [ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
• [ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
• [ ] Pull Request contains link to the JIRA issue
• [ ] Pull Request contains link to any dependent or related Pull Request
• [ ] Pull Request contains description of the issue
• [ ] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request checks
  Please add comment: Jenkins retest this

• for a specific pull request check
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests

• for quarkus branch checks
  Run checks against Quarkus current used branch
  Please add comment: Jenkins run quarkus-branch

• for a quarkus branch specific check
  Run checks against Quarkus current used branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

• for quarkus main checks
  Run checks against Quarkus main branch
  Please add comment: Jenkins run quarkus-main

• for a specific quarkus main check
  Run checks against Quarkus main branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

• for native checks
  Run native checks
  Please add comment: Jenkins run native

• for a specific native check
  Run native checks Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native

• for mandrel checks
  Run native checks against Mandrel image Please add comment: Jenkins run mandrel

• for a specific mandrel check
  Run native checks against Mandrel image
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel

• Full Kogito testing (with cloud images and operator BDD testing)
  Please add comment: Jenkins run BDD
  This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...