Support for agent install --base-path when using defend / endpoint security is included

Current feature :

Currently per [doc](https://www.elastic.co/guide/en/fleet/8.15/elastic-agent-cmd-options.html#_options_5) :
> --base-path
Install Elastic Agent in a location other than the [default](https://www.elastic.co/guide/en/fleet/8.15/installation-layout.html). Specify the custom base path for the install.
The --base-path option is not currently supported with [Elastic Defend](https://www.elastic.co/guide/en/security/8.15/install-endpoint.html).

Requested Feature :

Support for custom installation path when agent is using a policy that includes defend integration

Use case :

- User may be on virtualised environment and want to persist the agent folder by specifying a persistent location
- This feature is documented as not supported if the agent in question use a policy that include defend integration hence this causes a high number of offline then inactive agents by not being able to specify location of agent installation folder (agents then become inactive/hidden and need to be unenrolled)