This is in upstream opentelemetry-collector-contrib, so usable on any kind of collector deployment

a cue solution would be to have libraries never use concrete values but only defaults instead. so it would always be `string | *"foo"`, which is easy to forget.
maybe we could make it a tooling thing?

did anyone ever come up with another angle on that issue that's not either "specify all possibilities in advance, cry if you forgot" (helm, cue) or "change whatever you want, deal with the complexity" (jsonnet, tanka, kustomize")?