move command incorrectly relocates resources when a 'cluster' scope CRD is added.

We deployed crossplane with aws provisioner to our jenkins X cluster. This added some custom resource definitions including:
- **deployments**.apigatewayv2.aws.crossplane.io
- **secrets**.secretsmanager.aws.crossplane.io
The scope of these CRDs is 'Cluster'

During the next bootjob, the 'move' command relocated **all** deployments and secrets from config-root/namespaces to config-root/cluster then started pruning deployments including ingress-nginx, chartmuseum, etc.

Manually deleting the CRDs and rerunning the bootjobs restored the deployments.

Expected behaviour:
The move command should not be confused by the unrelated CRD and relocate resources.