`DISTRO-maven-central` freestyle job is failing in Quarkus extension

[yanavasileva]

Context

• After update to Quarkus 3.2. the job started failing as the quarkus tests are executed in the same reactor as the rest of subprojects. For more details check https://github.com/camunda/camunda-bpm-platform/issues/3419#issuecomment-1720916174

Acceptance Criteria (Required on creation)

• DISTRO-maven-central succeeds

Hints

• disable tests in Quarkus by default and only enable it when a specific Maven profile is executed. Or create a profile that disables the tests and add it to this particular job.
• alternative - disable the tests for the whole job instead only quarkus
  • cons - it's probably a safeguard to ensure we don't push SNAPSHOTs publicly that fail on tests.

Links

• is caused by https://github.com/camunda/camunda-bpm-platform/issues/3419
• initially reported in https://camunda.slack.com/archives/C036ZURJFMX/p1695372867213769

Breakdown

### Pull Requests
- [ ] https://github.com/camunda/camunda-bpm-platform/pull/3783

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[yanavasileva]

Decision: disable the tests only for quarkus in this job. Argument: keep the safeguard to not push broken Snapshot to maven central that users might consume. (example: building modules from master and pulling from maven central).

[yanavasileva]

Notes: The distro profile where the tests where disabled previously is activate by default for the sub modules as well. However, the tests are not disabled when no profile is specified.

[yanavasileva]

Test run: https://stage.ci.cambpm.camunda.cloud/view/all/job/sideprojects/job/7.20-platform-DISTRO-maven-central/8

[yanavasileva]

Decision: merge after the code freeze is lifted.

[yanavasileva]

TODO:

• [x] backport to 7.20