No way to define custom vector configuration portions other than sources, transforms and sinks in the Vector and VectorAggregator CRDs

[csabatuz-chess]

Context
We have some VRL that uses enrichment tables, and we planned to mount the necessary files into the vector pods, which we succeeded to do.

But then we realised that we have no way to define the enrichment tables because it's neither defined statically in the CRD, neither is there a ,,customConfig'' wildcard where the not yet explitly exposed configurations could be hacked in.

So we ended up falling back to the vector helm charts to deploy the aggregator to great sadness.

As vector is changing, new config options are expected, and a wildcard customConfig (while could be error prone) would provide the flexibility to be able to use these configs until the CRD catches up and makes the options explicitly exposed on it.