[jaeger-operator] Add ingressclasses to role.yaml so that the CRD has correct permissions when rbac.cluster.Role is set

[shivendoodeshmukh]

What this PR does

Add ingressclasses to role.yaml so that the CRD has correct permissions when rbac.cluster.Role is set

Which issue this PR fixes

• fixes #581

Checklist

• [X] DCO signed
• [X] Commits are GPG signed
• [X] Chart Version bumped
• [X] Title of the PR starts with chart name ([jaeger] or [jaeger-operator])
• [X] README.md has been updated to match version/contain new values

[FraPazGal]

Seems the operator still reports issues with this:

$ helm install jaeger-operator jaegertracing/jaeger-operator --version 2.55.0
$ kubectl logs $POD --namespace=default
...
W0731 08:01:25.681117       1 reflector.go:539] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:default:jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope
E0731 08:01:25.681154       1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:default:jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope

Probably requires adding the ingressclasses resource to the networking.k8s.io apiGroup in role.yaml