kubectl get VaultDynamicSecret doesn't find any dynamic secrets

Environment:
AKS cluster -- v1.26.6
Vault Secret Operator -- vault-secrets-operator-0.4.0
Kubectl -- v1.26.1

**Describe the bug**
I've installed VSO, and deploy a VaultAuth and a dynamic secret in default namespace, and try to retrieve the object from cluster, it has no return. ( I am able to do `kubectl get vaultauth`, it return as expected. )

```
(base) ~ kubectl get VaultDynamicSecret

No resources found in default namespace.
```

however, when retrieve with this command:
```
(base) ~ kubectl get vaultdynamicsecret.secrets.hashicorp.com
NAME AGE
vso-db-demo-create 5m57s
```

It can get object back from cluster. Can anyone explain what is this issue?

**To Reproduce**
Steps to reproduce the behavior:
see above

Application deployment:

```yaml
apiVersion: secrets.hashicorp.com/v1beta1
kind: VaultDynamicSecret
metadata:
name: vso-db-demo-create
namespace: default
spec:

# Mount path of the secrets backend
mount: database

# Path to the secret
path: creds/dev-database-role

# Where to store the secrets, VSO will create the secret
destination:
create: true
name: vso-db-demo-created

# Restart these pods when secrets rotated
rolloutRestartTargets:
- kind: Deployment
name: vso-db-demo

# Name of the CRD to authenticate to Vault
vaultAuthRef: dynamic-auth
```

Other useful info to include: `kubectl describe deployment ` and `kubectl describe ` output.

**Expected behavior**
I am expecting to see object show on my terminal, when do `kubectl get VaultDynamicSecret`

**Environment**
* Kubernetes version:
* AKS v1.26.6
* vault-secrets-operator version:
vault-secrets-operator-0.4.0

Kubectl -- v1.26.1

**Additional context**
Add any other context about the problem here.

Start by reproducing the two kubectl queries from the report against the VaultDynamicSecret resource and its secrets.hashicorp.com-qualified form. Inspect the installed Kubernetes resource discovery and CRD details to determine why the unqualified kind is not listed. Done means the intended kubectl command returns the vso-db-demo-create object, or the behavior is clearly documented as requiring the qualified resource name.

Written by the indexing model from the issue text.