Support syncing of configmaps?

**Is your feature request related to a problem? Please describe.**

Currently the vso crd is mainly used for syncing k8s secrets, but since this is a more k8s native flavored tool in hashicorp's tool box as compared to agent-inject and csi-mounts, would it be in scope to potentially to sync configmaps since configmaps which are almost as sensitive when compared to secrets?

**Describe the solution you'd like**

if we assume we already store configmaps in vault in a normal kv2 engine the vaultconfigmapspec could look like this:
```
apiVersion: secrets.hashicorp.com/v1beta1
kind: VaultConfigmap
metadata:
name: test-configmaps
namespace: default
spec:
destination:
create: true
name: test-configmaps
mount: configmaps
path: configmaps/test-configmaps
refreshAfter: 60s
type: kv-v2

```

Start by reviewing the existing VSO CRD and its Kubernetes Secret syncing behavior, then compare that flow with the proposed VaultConfigmap specification and KV-v2 data source. Define the scope and design for creating and refreshing ConfigMaps, including the example destination and refreshAfter behavior; completion should include agreed implementation and validation requirements.

Written by the indexing model from the issue text.