[9.0](backport #6907) Enhancement/6394 allow deb rpm to upgrade with endpoint tamper protection

[mergify]

• Enhancement

What does this PR do?

Updates the preinstall script for deb and rpm to stop the endpoint security service and remove the vault

Why is it important?

Currently when users upgrade their deb or rpm agents using their respective package managers, if there is endpoint running and if endpoint has tamper protection enabled, endpoint will become unhealthy. This PR fixes it by replicating what enpoint-security uninstall --uninstall-token <token> does in the deb/rpm preinstall script.

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

There shouldn't be anything disruptive for the users.

How to test this PR locally

• Start endpoint compatible VMs, one for deb one for rpm
• Build the agent for these two platforms
• Create an ESS deployment
• Create a policy, add endpoint integration
• Follow the "Add Agent" instructions and install the version that is shown on the instructions.
• Validate that both the agent and endpoint are healthy
• Upgrade the agent running either sudo apt install <Agent that you built> or sudo dnf install <Agent that you built>
• After the upgrade is done, validate that both the agent and the endpoint are healthy
• Just to be sure, validate that the new endpoint is still tamper protected
  • Try to uninstall agent without a token and see it fail
  • Try to uninstall agent with an uninstall token and validate that it is uninstalled
  • Beware that removing the agent using the package managers will indeed uninstall the agent but will leave endpoint. Use the elastic-agent command to uninstall.

Repeat the steps above but test same version upgrades.

• Install the agent you packaged from the branch.
• Enroll into fleet
• Install the same agent again with dpkg -i or rpm -Uvh --force
• Check the status of the agent and endpoint
• Validate that tamper protection is enabled

Note: When testing you may run into the following error

┌─ fleet
│  └─ status: (STARTING)
└─ elastic-agent
   ├─ status: (DEGRADED) 1 or more components/units in a failed state
   └─ endpoint-default
      ├─ status: (FAILED) Elastic Defend cannot run on an emulated architecture
      ├─ endpoint-default
      │  └─ status: (FAILED) Elastic Defend cannot run on an emulated architecture
      └─ endpoint-default-b73c5b0f-3b0a-4877-a531-35fdd9f9204f
         └─ status: (FAILED) Elastic Defend cannot run on an emulated architecture

This is related to the following bug #6866

Related issues

• Closes Allow DEB and RPM packages to supply an uninstall token when upgrading with Elastic Defend installed #6394
• Relates fix install prevention on Linux #6866

  ---

  This is an automatic backport of pull request Enhancement/6394 allow deb rpm to upgrade with endpoint tamper protection #6907 done by Mergify.

[elasticmachine]

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

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 3e05a91

Failed CI Steps

• x86_64:sudo: fleet

cc @kaanyalti

[cmacknz]

Reverted in #8638