fix(fms): fix prediction crash due to invalid thrust limit prediction

[BlueberryKing]

Fixes #[issue_no]

Summary of Changes

#9358 changed the way thrust limits were computed for predictions because the computation had to be separated between planes. In the separation, I introduced a bug that confused N1 for Corrected N1. This caused predictions to be nonsensical when the thrust limit was insufficient to keep climbing.

Screenshots (if necessary)

References

Additional context

Discord username (if different from GitHub):

Testing instructions

Make different flight plans at different weights, check that the T/C position makes sense and that it roughly coincides with the SimBrief prediction. Some deviation is expected due to different wind/temperature models.

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

[Saschl]

Quality Assurance TesterReport

Discord Username : saschl
Object of testing : #9719
Aircraft : A380X
Tier of Testing : 2
Date : 08/01/2025

Testing Process:

1. Flight from KJFK to KMCO
2. Observed TOC and TOD behaviour and placements seemed reasonable. No crashes could be observed
3. Loaded up another flightplan (EDDM-EDDF) and verified TOC placement being reasonable

Testing Results:
Passed

Media: