Elastic Defend arm64 is not supported on Windows yet

[intxgo]

What does this PR do?

This PR enhances elastic-endpoint spec to gracefully refrain from ever installing elastic-endpoint on Windows ARM, because Elastic Defend is not supported on it.

The win32 API used IsWow64Process2 is available only on Windows >= Win10, however Agent is currently compiled using Go 1.21 which requires at least Windows 10 or Server 2016.

The native architecture constants can be found here on MSDN web, however I believe it's unimportant to port them all since Elastic Defend is compiled only for x86_64 for Windows.

Reading environment variables could be an alternative solution, as Windows sets them by default, examples:

PROCESSOR_ARCHITECTURE=ARM64
PROCESSOR_IDENTIFIER=ARMv8 (64-bit) Family 8 Model 0 Revision   0, QEMU

PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 151 Stepping 2, GenuineIntel

PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 25 Model 97 Stepping 2, AuthenticAMD

However environment variables could be easily modified, therefore calling native API is better solution.

Why is it important?

Elastic Defend is not provided yet for Windows ARM (Microsoft Surface X or VM on Apple M1/M2/M3) but since Windows Elastic Agent amd64 works fine on Windows ARM in emulation people install it.

Handling gracefully the incompatibility enables installing Agent across a fleet of Windows AMD64 and ARM64 devices with the same policy.

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

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?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @intxgo? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[nfritts]

This looks good to me from Endpoints perspective

[pchila]

Aside from the small nitpick, the change looks good to me.
There is the small issue of the error in the endpoint spec though (CI is failing because of that)

[intxgo]

could you review this again since the implementation has changed significantly

@michalpristas @pchila

[michalpristas]

i think it looks good, fix from sysinfo is included for older windows versions as well.
haven't tested this on arm machine

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
76.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[cmacknz]

The one test failure here is unrelated:

	Received unexpected error:
        	            	failed to download https://snapshots.elastic.co/8.13.0-e2cda7bd/downloads/beats/elastic-agent/elastic-agent-8.13.0-SNAPSHOT-linux-x86_64.tar.gz: failed to write file /home/ubuntu/agent/.agent-testing/artifact/elastic-agent-8.13.0-SNAPSHOT-linux-x86_64.tar.gz: stream error: stream ID 1; INTERNAL_ERROR; received from peer

[cmacknz]

Going to force merge this one.