fix(konnect): Use correct label value of secret to store license

[randmonkey]

What this PR does / why we need it:

The Secret to store Konnect licenses was using an invalid label value causing that the Secret cannot be created/updated.

Which issue this PR fixes:

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[pmalek]

Ideally we'd add a test for that but I can see that this can be non insignificant effort to simulate failures to connect to Konnect in envtest or integration test.

Perhaps we add an issue for that? Not sure when we'd prioritize that though 🤔

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.3%. Comparing base (a278f8c) to head (704a6a5).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/konnect/license/client.go	0.0%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #7648     +/-   ##
=======================================
- Coverage   77.4%   77.3%   -0.1%     
=======================================
  Files        222     222             
  Lines      25869   25870      +1     
=======================================
- Hits       20039   20020     -19     
- Misses      4807    4830     +23     
+ Partials    1023    1020      -3     

☔ 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.

[randmonkey]

Ideally we'd add a test for that but I can see that this can be non insignificant effort to simulate failures to connect to Konnect in envtest or integration test.

Perhaps we add an issue for that? Not sure when we'd prioritize that though 🤔

I think we could check if the secret is created/updated in the current integration tests as the first step. I would create an issue for a test that simulate Konnect failures as it takes a significant effort.

[team-k8s-bot]

E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/16611875343

[team-k8s-bot]

E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/16613741821