feat(telemetry): introduce count for all Gateway API objects

[programmer04]

What this PR does / why we need it:

We decided to collect telemetry for all Gateway API objects in users' clusters.

Which issue this PR fixes:

closes #3649

Special notes for your reviewer:

It bumps package telemetry to version v0.0.5 that includes Kong/kubernetes-telemetry#143. Exclude directive has to be extended with sigs.k8s.io/gateway-api v0.7.0, because it's been discarded #4019 and pkg telemetry uses that version already

Test

kubernetes-ingress-controller/internal/manager/telemetry/manager_test.go

Line 37 in 2e5bcc8

func TestCreateManager(t *testing.T) {

is not extended, because of issue with mocking. For more comprehensive tests in telemetry pkg the issue has been created Kong/kubernetes-telemetry#144

I'm proposing new way for testing it e2e with usage of envtest approach proposed in #4094 and #4101. Maybe it should be extended with mesh discovery too, and the above mentioned TestCreateManager removed entirely - something to consider (and maybe create separate issue). For more standardised approach to envtest check issue #4099.

I've run proposed test locally in a loop and I haven't observed flakiness. Timeouts were adjusted empirically to ensure that test will pass, for weak hardware (like GH managed runners) it was a problem to have TelemetryPeriod set e.g. to 100ms (on local machines it used to pass without any issue).

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]

I believe we're now at the point where we can try to address the issue with the fake objects.

If https://github.com/Kong/kubernetes-ingress-controller/blob/2e5bcc8c8034daeab4bd8558c8768450619f379f/internal/manager/telemetry/manager_test.go cannot be made to work with fake objects then I'd extend it with an envtest based test so that we can actually test the counters end to end. There have been occasions where the telemetry reporting failed after release and we needed to fix with a subsequent release which caused issues with our telemetry data.

[codecov]

Codecov Report

Patch coverage: 100.0% and project coverage change: +0.4 🎉

Comparison is base (8f34e26) 60.3% compared to head (0be1126) 60.7%.

❗ Current head 0be1126 differs from pull request most recent head a77eb66. Consider uploading reports for the commit a77eb66 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #4058     +/-   ##
=======================================
+ Coverage   60.3%   60.7%   +0.4%     
=======================================
  Files        150     150             
  Lines      16745   16747      +2     
=======================================
+ Hits       10099   10175     +76     
+ Misses      6014    5926     -88     
- Partials     632     646     +14     

Impacted Files	Coverage Δ
internal/manager/telemetry/manager.go	60.3% <100.0%> (+15.1%)	⬆️

... and 7 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.