v1.1.0 Longevity test

[ciarams87]

Proposed changes

Problem: We want to run our longevity test for every release and capture the findings.

Solution: Run the longevity test and commit the results.

Please focus on (optional): There was an error in the setup of the prometheus logging, so the NGINX metrics were not correctly exported.

Closes #ISSUE

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

[netlify]

✅ Deploy Preview for nginx-gateway-fabric canceled.

Name	Link
🔨 Latest commit	72f5f09
🔍 Latest deploy log	https://app.netlify.com/sites/nginx-gateway-fabric/deploys/657837470f108d00083a260a

[kate-osborn]

I do think it's worth it to re-run the longevity tests so that we have metrics to compare 1.3 to, but I don't think it should block the release. There are no new errors, memory leaks, or CPU spikes that require investigation. Reloads are well-covered by other NFR tests I'm not sure how much insight we are getting from the nginx stub-status metrics.