Enable and update endpoint for telemetry for longevity tests

[salonichf5]

Proposed changes

We want to report telemetry when running longevity tests to the development endpoint.

Problem: Users want to get telemetry reports when running longevity tests to simulate a live environment.

Solution: To provide live telemetry reports when running longevity tests, we have enabled telemetry for the test when lavel is longevity and updated the workflow that creates the binary for release to update the TELEMETRY_ENDPOINT to the dev endpoint.

Note: I will be updating the binary building workflow to be triggered on a push to release branch. I tested it on the condition of pull_request to verify variables are set properly.

Testing: Manual testing using Github actions and running longevity tests.

Running make start-longevity-test

make start-longevity-test
CI=false ./scripts/run-tests-gcp-vm.sh
.
.
.
 Installing NGF with command: helm install --debug ngf-longevity /home/username/nginx-gateway-fabric/charts/nginx-gateway-fabric --create-namespace --namespace nginx-gateway --wait --set nginxGateway.snippetsFilters.enable=true --set nginxGateway.image.repository=gcr.io/f5-gcs-7899-ptg-ingrss-ctlr/nginx-gateway-fabric --set nginxGateway.image.tag=release-1.5-rc --set nginxGateway.image.pullPolicy=Always --set nginx.image.repository=gcr.io/f5-gcs-7899-ptg-ingrss-ctlr/nginx-gateway-fabric/nginx-oss --set nginx.image.tag=release-1.5-rc --set nginx.image.pullPolicy=Always --set nginx.plus=true --set service.type=LoadBalancer --set service.annotations.networking\.gke\.io\/load-balancer-type=Internal --set nginxGateway.productTelemetry.enable=false --set nginxGateway.productTelemetry.enable=true --set nginxGateway.config.logging.level=debug

Product Telemetry set to true

--set nginxGateway.productTelemetry.enable=true 

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 #1781

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.86%. Comparing base (f56f525) to head (9bdb79b).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2824   +/-   ##
=======================================
  Coverage   89.86%   89.86%           
=======================================
  Files         107      107           
  Lines       10997    10997           
  Branches       50       50           
=======================================
  Hits         9883     9883           
  Misses       1054     1054           
  Partials       60       60           

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

[sjberman]

I'll defer to @lucacome to make sure this logic is correct. It looks like we have to enable building with the dev endpoint for all pushes to the release branch in order build the -rc images with it, which we use for the longevity tests. But this shouldn't be an issue because when we tag for a release, it'll fail the condition and use the prod endpoint instead.