fix(a380x/mfd): Updated disabled input field styling

[jet2code]

Fixes #9734

Summary of Changes

• Added $display-light-grey border to mfd-input-field-container.disabled:hover
• Changed mfd-input-field-text-input.disabled text color to $display-dark-grey to match other disabled buttons and input fields.

This visually clarifies any confusion that pilots may have regarding the input field and its disabled state.

Screenshots (if necessary)

Before

After

References

Additional context

Discord username: john.xyz

Testing instructions

• Ensure other input fields, disabled or not, are displayed correctly with no regressions.

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

[G-DRAW]

Great job on the update.
I just want to clarify that the latest indication on these data entry fields are correct, but this layout appears after the first engine start.

There CPNY RTE and ALTN RTE fields with NONE in them should still display in blue after initialisation and before engine start.

I've also created another Issue for the missing amber boxes in the relevant entry fields, before the INIT A Page is filled out.

[flogross89]

Thanks, this change makes sense. After you fixed the changelog, we can merge this PR.

[flogross89]

please put change at the end of all 0.13.0 changes

[flogross89]

@G-DRAW The difference in CPNY/ALTN RTE stem from the fact that those two fields are still disabled in our FMS due to them not being implemented yet (also, since we don't really use CPNY RTEs in flight simming, there might not be a use for them). Once we enable them, they will also stay enabled after engine start, meaning they will show with cyan font.