ConfigMap manifest misconfigured in example

### What happened?

The ConfigMap manifest is missing the namespace from the metadata, so it gets created in the default namespace, hence the pod can't start up.

### Velero UI version

0.9.3

### Velero version

N/a

### Deployment mode

Kubernetes

### Relevant log output

```shell

```

### Additional context

```markdown

```