NGINXaaS: Add display name to metrics catalog

[arpith-f5]

Proposed changes

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

Problem: Platform metrics are queried using Display Names in Azure Monitor. Add Display Names to metrics catalog for easy lookup
Solution: Add a new column for Display Name

Testing: local testing

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.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[arpith-f5]

I have hereby read the F5 CLA and agree to its terms

[ryepup]

do we need a redirect for this so any old links to getting-started still work?

[JTorreG]

if you decide you do, please request it in the docs channel in slack for the docops engineers to create it

[ryepup]

future: I spot checked a few and they look right, but copilot makes me nervous. These are all supposed to match https://github.com/nginxinc/nalb-shared/blob/main/nginx/native-metrics/spec.json, right? Maybe copilot could write a script to generate these tables from that file, then we'd have something deterministic. Maybe the next time we need to change these tables.

[arpith-f5]

yes they are all supposed to match https://github.com/nginxinc/nalb-shared/blob/main/nginx/native-metrics/spec.json. I asked co-pilot to generate a script and it did a decent job but there are subtle differences in the metrics catalog that makes it hard from being generated from the spec alone. The column 'Roll-up per' is not available in the spec and there are issues with capitalization and ordering. If these need to be fixed manually then it defeats the point of having a script. Perhaps we can drop the 'Roll-up per' column in metrics catalog and change the capitalization and ordering in the spec to match the current format but I don't know if LIFTR/Geneva will like that