add non-fatal endpoint security exit code

[intxgo]

What does this PR do?

Adds exit code 284 to non fatal exit codes for endpoint security component.

Why is it important?

See related issues, the change introduced only posix exit code.

Background story: The exit code was 284 since the beginning for all platforms, but later on we changed it for posix to fix bash scripts. The problem is that shell scripts expect byte size return codes, so 284 becomes 28 when casted to byte size.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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

• Relates Allow Endpoint service to keep running if its install exit code is non-fatal #9320

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-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[intxgo]

@ycombinator was your PR already included in any release? If not, I guess we can simply skip release notes fragment for this quick fix.

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[cmacknz]

You need a changelog fragment, the CI failure for FIPS should hopefully be resolved now.

[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

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 88a80a3

Failed CI Steps

• arm:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default

History

• 💔 Build #26024 failed f070c3d

cc @intxgo

[github-actions]

@Mergifyio backport 8.17 8.18 8.19 9.0 9.1

[mergify]

backport 8.17 8.18 8.19 9.0 9.1

✅ Backports have been created

• #9711 [8.17] (backport #9687) add non-fatal endpoint security exit code has been created for branch 8.17
• #9712 [8.18] (backport #9687) add non-fatal endpoint security exit code has been created for branch 8.18
• #9713 [8.19] (backport #9687) add non-fatal endpoint security exit code has been created for branch 8.19
• #9714 [9.0] (backport #9687) add non-fatal endpoint security exit code has been created for branch 9.0
• #9715 [9.1] (backport #9687) add non-fatal endpoint security exit code has been created for branch 9.1