MCPRegistry e2e tests

[dmartinol]

First bunch of tests to address #1749
It also depends on #2016 which should be committed first

• Fixes never-ending reconciliation loop by comparing the status fields instead of always updating the updated status (this would cause an immediate reconciliation)
• Adds a test/e2e/operator/registry_lifecycle_test.go initial test to prove the capabilities of ginkgo as the testing framework for orchestrated workflows

Questions to be answered:

• Where do we keep this files, is the current location suitable?
• Should we call them from the operator-e2e-test task?

[codecov]

Codecov Report

❌ Patch coverage is 31.25000% with 143 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.52%. Comparing base (718e2cb) to head (f93e3b3).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
...thv-operator/controllers/mcpregistry_controller.go	0.00%	80 Missing ⚠️
cmd/thv-operator/pkg/sync/manager.go	61.85%	25 Missing and 12 partials ⚠️
...md/thv-operator/pkg/mcpregistrystatus/collector.go	10.34%	25 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2017      +/-   ##
==========================================
- Coverage   48.64%   48.52%   -0.12%     
==========================================
  Files         240      240              
  Lines       30264    30344      +80     
==========================================
+ Hits        14721    14725       +4     
- Misses      14439    14504      +65     
- Partials     1104     1115      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dmartinol]

I've added more tests covering most of the sync, data sources and filtering options and workflows.
I think it should be enough for now, especially if we're going to plan for some extensive review of the controller, like moving some of the functions to the thv-registryapi` service.

[jhrozek]

I was mostly focusing on the controller changes which look good with one question about the has. In the test code, the question is just whether we want to remove some of the unused code or whether you want to keep it for later.

[jhrozek]

I acked this patch if you want to merge now - I know on Slack you said you also want to integrate with Taskfile targets, but let me know if this should be done later.

[dmartinol]

all tests passed @jhrozek

[jhrozek]

epic! Let's merge