Wait job can conflict with other resources in the cluster

Summary

(Summarize the bug encountered or feature requested concisely)

I happen to have two types of mattermost CRDs in my cluster, one from mattermost, then a separate one for crossplane under a separate api group. We should include the api group as part of the kubectl command so that it is guaranteed it is calling the correct one deployed by the chart.

Steps to reproduce

(How one can reproduce the issue - this is very important)

What is the current behavior?

(What actually happens)

What is the expected behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

If we could update this line to include the api group as well, that would be awesome. For example:

kubectl get $resourcename --namespace=$resourcename -o jsonpath='{.items[0].status.state}' -> kubectl get $resourcename.installation.mattermost.com --namespace=$resourcename -o jsonpath='{.items[0].status.state}'

/cc {put CODEOWNERs @githandles here}