feat(a380x/mfd): Add DATA/NAVAIDS page

[jet2code]

Planned

• Add ability to create and store navaids
• Add elevation data

Identify:

• ILS
• LOC
• ILS/DME
• VOR
• DME
• NDB
• VOR/DME

Summary of Changes

• Added navaids under DATA pages.
• Support for all radio navaids except for GLS

Screenshots (if necessary)

References

Additional context

Discord username: john.xyz

Testing instructions

1. Go to DATA --> NAVAID
2. Search a navaid of each class listed above under the Identify header
3. Ensure data and layout is accurate

How to download the PR for QA

Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, find and click on the PR Build tab
4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

[jet2code]

If possible, I would like some insights on some of these items:

1. Elevation data (is there a way we can fetch already that I am not aware of?)
2. Other pages also identify some localizers and ILSs without DME as ILS/DME. Is this known or is there a potential fix that could be used?
3. I left some HTML code for the PILOT STORED NAVAID page. I was told by another contributor that I will likely not need to worry about it for now however if you would like me to comment anything out, please let me know.

I believe that should be all. Any input on the rest of the implementation will be greatly appreciated!

[tracernz]

Only MSFS2024 has enough data to determine LOC vs ILS vs ILS/DME. Elevation is available on all the interfaces where it’s applicable. Pilot stored nav aids are fully implemented on the A32NX but I’m not sure of the state on A380X.