🐛 fix: extension controller should requeue extensions when catalogs change

[joelanford]

Description

There is a bug in the watch setup of the extension controller where watch events for catalog updates are translated to reconcile requests that bear the name of the catalog, which means it is trying to reconcile an Extension with the same name as the catalog that evented.

This isn't the intention. The intention is to requeue all Extensions when a catalog changes, since that might mean a new/better version is available for us to consume.

Reviewer Checklist

• API Go Documentation
• Tests: Unit Tests (and E2E Tests, if appropriate)
• Comprehensive Commit Messages
• Links to related GitHub Issue(s)

[codecov]

Codecov Report

Attention: 17 lines in your changes are missing coverage. Please review.

Comparison is base (d51dfe6) 84.53% compared to head (1cbab3b) 76.40%.
Report is 22 commits behind head on main.

Files	Patch %	Lines
internal/controllers/extension_controller.go	0.00%	17 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #643      +/-   ##
==========================================
- Coverage   84.53%   76.40%   -8.13%     
==========================================
  Files          20       24       +4     
  Lines         931     1208     +277     
==========================================
+ Hits          787      923     +136     
- Misses        100      234     +134     
- Partials       44       51       +7     

Flag	Coverage Δ
e2e	53.64% <0.00%> (-6.19%)	⬇️
unit	70.57% <0.00%> (-9.72%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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