Add Ingress Annotation List to Telemetry

[AlexFenlon]

Proposed changes

This adds a list of configured and filtered ingress annotations whether it is a mergeable or standard ingress, it collects the list of unique annotations and displays them in the telemetry log below.

Annotations that will show in telemetry are any annotation that has the following:

	"nginx.org",
	"nginx.com",
	"f5.com",
	"ingress.kubernetes.io/ssl-redirect",

Resolves: #4884

This log is from a mergeable ingress where the nginx.org/mergeable-ingress-type annotation is in both master and minions and proxy-set-headers only in one minion:

I0509 11:36:25.458992       1 collector.go:143] Telemetry data collected: {Data:{ProjectName:NIC ProjectVersion:3.6.0-SNAPSHOT ProjectArchitecture:amd64 ClusterID:707783d6-be8b-4ce0-ad22-3545281b9bb9 ClusterVersion:v1.28.3 ClusterPlatform:other InstallationID:22bd83da-822e-4cf9-8ff6-a6dc08256782 ClusterNodeCount:1} NICResourceCounts:{VirtualServers:1 VirtualServerRoutes:0 TransportServers:0 Replicas:1 Secrets:5 Services:3 Ingresses:3 IngressClasses:1 AccessControlPolicies:0 RateLimitPolicies:2 JWTAuthPolicies:1 BasicAuthPolicies:1 IngressMTLSPolicies:1 EgressMTLSPolicies:0 OIDCPolicies:0 WAFPolicies:0 GlobalConfiguration:false IngressAnnotation:[nginx.org/proxy-set-headers nginx.org/mergeable-ingress-type]}}

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[ADubhlaoich]

LGTM docs-wise but not approving since the PR is primarily code based.