We are supporting multiple services for the elastic-agent:

• centos-systemd
• centos
• cloud
• debian-systemd
• debian

And each of them means having a separate dir in the services layout.

1. We could remove the vanilla centos & debian services, are they are not used nor going to be used.
2. We are hardcoding the centos-systemd name for the service, which is causing strong coupling with the installer structs, and service names. Simplifying the layout we could simply rename the service (and eventually the container name) for elastic-agent, period.

cc/ @adam-stokes