Is your feature request related to a problem? Please describe.
I know, I know, it's called the External Secret operator.

I make heavy use of Hashicorp Vault for storing data that is not really secret, just needs to be accessed by several teams and machines and there is no need for it to be hidden in-cluster.
I'm not sure there is a nice developer and user UX for this, so feel free to disregard, but I'll try below.

Describe the solution you'd like
Creating new {Cluster,}ExternalConfigMap CRD for this is clearly overkill and would increase the maintenance burden enormously.

The simplest solution looks to me adding a kind: {ConfigMap,Secret} (defaults to Secret) into the target.template of an ExternalSecretSpec.
Validation should then be performed on target.template.type, which must be empty if kind is ConfigMap.
Everything else can stay as-is as far as I can see, thankfully Secrets and ConfigMaps are really similar.

Describe alternatives you've considered
Just using Secrets and telling the dev teams to decrypt them by hand, they'll live with it if you guys don't like this.

Additional context
I've searched for ConfigMap-related issues on GH, none popped up, feel free to direct me if this was already rejected.