Follow up testing work from the addition of installation flavors

[cmacknz]

Follow up testing work from #6542

Upgrades for agents with an installed flavor

• Install an agent with the default, basic flavor and upgrade it to another version that supports flavors. After the upgrade none of the binaries from the servers flavor should be on disk.
• Install an agent with the servers flavor and upgrade to another version that supports flavors. After the upgrade all of the binaries from the servers flavor should be on disk.

Integration test for components with additional file dependencies

• Ensure the component_files lists of osquerybeat, apm-server, endpoint-security, and cloudbeat are correctly preserved for the appropriate flavors. Ideally, confirm the integration can be installed and remain healthy as a basic sanity check.
  • endpoint-security is already covered by an integration test but the others are not.
  • Perhaps this would be best be done by extending the existing installation tests to look at what their spec files declare and ensure the files are preserved.

    elastic-agent/testing/integration/install_test.go

    Lines 166 to 173 in 093fb58

    	t.Run("check components set",
    	testComponentsPresence(ctx, fixture,
    	[]componentPresenceDefinition{
    	{"agentbeat", []string{"windows", "linux", "darwin"}},
    	{"endpoint-security", []string{"windows", "linux", "darwin"}},
    	{"pf-host-agent", []string{"linux"}},
    	},

[elasticmachine]

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

[elasticmachine]

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

[michalpristas]

note: checking for files defined in spec file is not an option, component files is a filter and does not require files to be present. e.g some files present only on linux, exe paths only on windows. this information is not part of the filter definition