[BUG] Starboard CRDs out-of-sync if deployed using ArgoCD

[David Calvert]

What steps did you take and what happened:

• I deployed the starboard-operator helm chart using an ArgoCD application and noticed a small issue.
  The starboard operator get's installed and it's working perfectly, but the starboard CRDs are staying out-of-sync in ArgoCD.
  This is because the categories: field of all starboard's CRD is an empty list and get's dropped by Kubernetes.
  While this might not be an issue for starboard and kubernetes, it is for argocd that sees a diff between the desired state and the live state.

Screenshots:

• Broken: https://raw.githubusercontent.com/dotdc/media/main/github-issues/2022-05-30-starboard-crds-broken.png
• Diff Detail : https://raw.githubusercontent.com/dotdc/media/main/github-issues/2022-05-30-starboard-crds-detail.png
• Fixed: https://raw.githubusercontent.com/dotdc/media/main/github-issues/2022-05-30-starboard-crds-fixed.png

What did you expect to happen:

• I expect to have all starboard CRD in sync after the helm chart deployment.

Anything else you would like to add:

• Coming back with a PR to fix

[Miscellaneous information that will assist in solving the issue.]

Environment:

• Starboard version (use starboard version): v0.15.4
• Kubernetes version (use kubectl version): v1.20.15-eks (aws eks)
• OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): archlinux