Break up helm edot-collector into templates to allow for various teams to own certain configs

It has been suggested to breakup the helm charts at `/deploy/helm/edot-collector/` into templates to allow different teams to own certain aspects of the config in helm charts, see comment [here](https://github.com/elastic/elastic-agent/pull/16463#discussion_r3922583896).

> As mentioned to @mariapoutachidou - longer term Signals might want to suggest a similar approach as in Elastic Agent helm where they have templates which would allow ownership of just the configs for various Signals teams on specific Signal config and give the helm deployment for edot-collector to Elastic Agent team.
e.g. https://github.com/elastic/elastic-agent/tree/main/deploy/helm/elastic-agent/templates/integrations

Start by inspecting the Helm chart under /deploy/helm/edot-collector/ and compare its organization with deploy/helm/elastic-agent/templates/integrations. Review the linked discussion for the intended ownership boundaries. Done means the chart is split into templates so different teams can own specific configuration areas while Elastic Agent retains ownership of the deployment.

Written by the indexing model from the issue text.