fix duplicated CreateIngressEx calls

[matei]

Proposed changes

Problem:
when the ingress controller pods start, we have:

1. Informers fire ADD events for every existing resource (every Service, every EndpointSlice, every Secret, etc.)
2. Each one gets queued and processed individually via syncService(), syncEndpointSlices(), syncSecret(), etc.
3. Each of those calls FindResourcesForService / FindResourcesForEndpoints / FindResourcesForSecret → all hitting
   findResourcesForResourceReference
4. Each call returns the same Ingress duplicated N times (once per host)

Point 4 is the issue in findResourcesForResourceReference: if an ingress is serving 50 hosts, this method will duplicate the same IngressConfiguration / VirtualServerConfiguration / etc. object in result 50 times.
This is causing a big delay from container start to container ready (in our tests 2min+ for an ingress with 57 hosts).

Solution:
simple de-duplication in findResourcesForResourceReference. With the fix to de-duplicate, this time is reduced to 2-3s

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

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[matei]

I have hereby read the F5 CLA and agree to its terms

[AlexFenlon]

Hi @matei, thank you for the PR.

Can you please rebase and commit again using the @matei user or accept the CLA using the @MateiStefanescu-MRM user to pass our F5 CLA.

[vepatel]

Hey @matei thanks for the PR, can you please create an issue in the repo with the same description as the PR and attach it to the PR please,
this'll help us prioritise this in our community calls

[matei]

Hey @matei thanks for the PR, can you please create an issue in the repo with the same description as the PR and attach it to the PR please, this'll help us prioritise this in our community calls

Hey @vepatel, this is related to this issue

[Copilot]

Pull request overview

This PR addresses a startup-time performance issue where findResourcesForResourceReference can return the same resource multiple times (once per host key), causing downstream processing to repeat work for multi-host resources.

Changes:

• Add de-duplication logic to findResourcesForResourceReference using Resource.GetKeyWithKind() to ensure each matching resource is returned at most once.
• Apply the same de-duplication across both hosts and listenerHosts scans.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This change adds de-duplication behavior in findResourcesForResourceReference, but there’s no unit test covering the regression scenario described in the PR (a single resource associated with many host keys returning duplicates). Please add a test case with an Ingress (or VirtualServer) that has multiple hosts and references the same Service/Secret, and assert the returned slice contains that resource only once.

[matei]

Added test case