ci(smoke-test): multi-arch container smoke test

[megglos]

Description

Docker builds and smoke tests are only run on Linux machines as building docker containers on macOS and windows runners introduces complexity to the CI setup that we consider not worth the effort:

• macOS runners require the setup of colima as a docker runtime which adds another 1.5-2m to the runtime
• on macOS testcontainers failed to detect the docker environment unless additional environment variables have been set
• some docker related actions are not supported on windows runners like docker/build-push-action
• the docker setup on Githubs windows runners seems to be bound to the windows/amd64 platform, see e.g. this log

Usage of native arm64 runners is listed as a separate sub-task on #10986.

Related issues

closes #11020

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

• The changes are backwards compatibility with previous versions
• If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

• There are unit/integration tests that verify all acceptance criterias of the issue
• New tests are written to ensure backwards compatibility with further versions
• The behavior is tested manually
• The change has been verified by a QA run
• The impact of the changes is verified by a benchmark

Documentation:

• The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
• If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

[github-actions]

Test Results

   964 files  +    5     964 suites  +5   1h 52m 20s ⏱️ + 10m 41s
7 900 tests +398  7 893 ✔️ +398  7 💤 ±0  0 ❌ ±0 
8 106 runs  +404  8 097 ✔️ +404  9 💤 ±0  0 ❌ ±0 

Results for commit b74fbdb. ± Comparison against base commit 601c718.

♻️ This comment has been updated with latest results.

[npepinpe]

👍 Generally looks good. Had some comments, nothing major.

[npepinpe]

👍

Looks great! Some comments but nothing which needs another review

[npepinpe]

💭 it's rare to encounter a wild "ado" 😄 I guess it's technically appropriate it here though ;)

[npepinpe]

🔧 Surefire already has a property for this, e.g. excludedGroups. So if you just set it to -DexcludedGroups then you don't need to define an additional property. I guess it wouldn't play nice with profiles which may set additional excluded groups? I'm not 100% sure there, but it shouldn't be an issue here specifically.

[megglos]

good point!
will actually go for the already available property, especially for this particular case "don't run container tests" I guess it would be nice if it also applies to different profiles, if we reuse that tag at some point.

If we hit issues with overrides we may address that then.

[megglos]

bors r+

[zeebe-bors-camunda]

Build succeeded:

• Test summary