[CI] Skip new ARM tests

[pazone]

What does this PR do?

Relates https://github.com/elastic/ingest-dev/issues/4610

ARM tests make tests flaky

Why is it important?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[alexsapran]

While skip supports true|false it also can support the comment so that we could use this instead

Suggested change

	skip: true
	skip: Due to https://github.com/elastic/ingest-dev#4610

So the reason will be show in the UI.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube