Add categories to provider CRDs

[ytsarev]

Description of your changes

Include provider CRDs into the relevant API categories.

Fixes #114

Enables getting Workspaces in the output of kubectl get managed and kubectl get terraform

Similar changes to ProviderConfig and ProviderConfigUsage for getting into kubectl get provider and kubectl get terraform output

Signed-off-by: Yury Tsarev yury@upbound.io

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

k apply -f examples/workspace-remote.yaml
workspace.tf.crossplane.io/example-remote configured

k get managed
NAME                                        READY   SYNCED   AGE
workspace.tf.crossplane.io/example-remote           False    5m21s

k get terraform
NAME                                                                        AGE     CONFIG-NAME   RESOURCE-KIND   RESOURCE-NAME
providerconfigusage.tf.crossplane.io/44d34bbb-c4e0-49c9-a7ec-27e496ed75a9   5m29s   default       Workspace       example-remote

NAME                                        READY   SYNCED   AGE
workspace.tf.crossplane.io/example-remote           False    5m29s

NAME                                      AGE
providerconfig.tf.crossplane.io/default   14m


k get provider
NAME                                                                        AGE     CONFIG-NAME   RESOURCE-KIND   RESOURCE-NAME
providerconfigusage.tf.crossplane.io/44d34bbb-c4e0-49c9-a7ec-27e496ed75a9   5m38s   default       Workspace       example-remote

NAME                                      AGE
providerconfig.tf.crossplane.io/default   14m

[bobh66]

LGTM