Add nginx one console connection telemetry field

[salonichf5]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: We want to know how many clusters are connected to NGINX One console.

Solution: Reports product telemetry to report if cluster is connected to NGINX One console

Testing: Unit tests, functional tests

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

Closes #3119

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

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

[salonichf5]

Do we add release notes for adding telemetry fields since its user information?

[codecov]

Codecov Report

❌ Patch coverage is 40.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.91%. Comparing base (ca42cd7) to head (b16f122).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/controller/manager.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3717      +/-   ##
==========================================
- Coverage   86.95%   86.91%   -0.04%     
==========================================
  Files         128      128              
  Lines       15962    15965       +3     
  Branches       62       62              
==========================================
- Hits        13879    13876       -3     
- Misses       1917     1922       +5     
- Partials      166      167       +1     

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sjberman]

Do we add release notes for adding telemetry fields since its user information?

@salonichf5 I don't think we have in the past, though we do update our documentation page that talks about this.

[bjee19]

Have you already done the testing on the xcdf side and updated the schema on that side?

[salonichf5]

Have you already done the testing on the xcdf side and updated the schema on that side?

no, waiting on databricks to start working for me.

[bjee19]

Approving for now, though probably shouldnt be merged until xcdf testing is completed, also should update https://github.com/nginx/documentation/blob/main/content/ngf/overview/product-telemetry.md

[salonichf5]

Docs PR - nginx/documentation#944

[salonichf5]

verified that the field shows up as expected on Dev and prod endpoints.