Disable SVE in JAVA_OPTS for IT Mac M4 compatibility

[abremard]

Describe the bug

When running integration tests locally on a Mac M4, we're running into a known compatibility issue. An initial attempt at applying the fix was done in this PR but unfortunately it's breaking CI. For Mac M4 users, they can locally run integration tests with the setup in the PR but that change is currently breaking docker builds when executing github CI actions. We should investigate why is it so and what fix can be done to ensure compatibility for both M4 users and CI.

Expected behaviour

Integration tests can be run by M4 users and through CI

To Reproduce

Run integration tests locally

Environment observed:

• Optimize mode(s):
• Optimize version(s):
• Database(s) (Elasticsearch/OpenSearch):

Breakdown

Pull Requests

Preview Give feedback

No tasks being tracked yet.

Bug Lifecycle

For managing the issue lifecycle, please use the workflow commands. You can see the available
commands by writing /help as a comment on this issue.

QA Verification

Is this bug reproducible?

• Yes. If so:
  • The bug description is clear
  • The steps to reproduce are clear
  • The environments observed are correct and complete
• No

Review

Engineering Review

• All code targeting the main branch has been reviewed by at least one Engineer
• The PR targeting the main branch has been approved by the reviewing Engineer
• If the API has changed, the API documentation is updated
• All other PRs (docs, controller etc.) in the breakdown have been approved

QA Review

• The change is implemented as described on all target environments/versions/modes
• The documentation changes are as expected

Completion

• All Review stages are successfully completed
• All associated PRs are merged to the main branch(es) and stable branches
• The correct version labels are applied to the issue

[maff]

@abremard I'm running into the same issue - looks like this will be fixed soon by the next Docker Desktop release: docker/for-mac#7583 (comment)

[abremard]

Thanks for sharing this @maff !

[abremard]

I'm closing this issue since it's been resolved with Docker Desktop 4.39.0