Remove `es` shortName from eventsources CRD

[davidgamba-au]

Is your feature request related to a problem? Please describe.
The es shortName is used for externalsecrets which is way more common than eventsources.

I rarely have to look at my eventsources with Argo Events/Workflows.

Describe the solution you'd like
Remove the es shortName from the Argo Events CRDs so that it doesn't shadow my externalsecrets shortName.

Describe alternatives you've considered
A mutation webhook maybe, or some post install edit of the CRD but I really don't see why taking the same shortName of a very popular widely used CRD.

Additional context

$ kubectl api-resources | grep -E '\bes\b'
eventsources                        es                                     argoproj.io/v1alpha1                         true         EventSource
externalsecrets                     es                                     external-secrets.io/v1beta1                  true         ExternalSecret

Because argo goes first alphabetically its shortNames will always take precedence.

---

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

[DavidGamba]

Context: kubernetes-sigs/cluster-api#870 (comment)

There is currently no way to choose the relative priority ordering for custom resources when you execute kubectl get. What happens is kubectl downloads the API discovery document from the apiserver and stores it in a local file cache. The discovery document contains a list of all the resources the apiserver offers. Whichever cluster resource is first in the list is the one that kubectl get will retrieve.