Proposal

Support defining multiple configRef secretName values to build a policy from multiple secrets.

Use case. Why is this important?

I've manage some fairly large system generated Elastic Agent policies for Standalone agents. I've recently been hitting an issue where the policies have grown past Kubernetes Secret Size limit, 1 MiB, and have had to do some hacky stuff to try and bring the size down.

Ideally, I should be able to provide a number of secrets that the Elastic Agent/ECK operator can merge together to form a singular policy file for the agent when deployed, allowing for configs >1 MiB.