feat(GSX): 380 Refuel/Door Sync, Harmonize GSX Code and External Power-Sync for 320+380

Fixes #9383 [maybe 9287 too]

Summary of Changes

Well I just wanted to Port PR 8407 to the 380 and get the Cargo Doors synched and it grew a bit bigger 😅

380: Refuel/Defuel automatically starts when GSX Hose is connected
380: Instant Fuel allowed with GSX Fuel Sync
380: Cargo Doors are synced with GSX (being automatically opened and closed while Boarding/Deboarding)
380: FOB (Total) and ETA added to Fuel Page
380/320: Harmonized GSX Code (except Payload Synch) in shared Host/Module
380/320: Better handling for FOB >= planned (Defuel / No Action) Situations with GSX
380/320: Bettor Error-Handling while refueling (e.g. Couatl restarted)
380/320: Override GSX Progressive Refuel Setting to disabled
380/320: EFB Changes Label "Call GSX Refuel" to "GSX Refuel requested" when the GSX Refuel Service is requested (overall rework of format class/label logic)
380/320: Import SimBrief Button on Fuel Page is hidden when planned SB Value is set or refueling in progress (general)
380/320: Disable Slider and Input Box when (FBW) Refuel/Defuel Process is active
380/320: Play/Start Button now also hidden/disabled when Rate is Instant and GSX Refuel is requested
380/320 - already incorporating PR 9470 - New GSX Power Synch Feature (+EFB Option) to synchronize External Power Available with GSX

Screenshots (if necessary)

References

Additional context

Note for Cases with FOB >= planned/desired: GSX can't detect if the Aircraft is defueling and has no Means to send the truck away - we need an Increase of Fuel. So the proposed PR sets the desired Fuel temporarily to a lower Amount and starts Defuel. After that an instant Refuel to the actual desired Value is started. => GSX in any Case gets a Signal that Fuel is finished and the Truck will leave. On the A380 there is currently a Bug within GSX in this Detection, hence the Fuel-Difference is quite high there (5000kg). Once that is fixed in GSX the Value can be lowered in the Future.
Note for Error-Handling: If the Fuel Hose gets disconnected during De/Refueling (GSX Crash, Simconnect Issues, User restarts Couatl), the Integration will set the desired Fuel instantly.
Note on Power-Synch: Power will be reported as avail when Jetway or GPU is connected (== 5). Power will be removed when GPU and Jetway are disconnected or Pushback is active (== 5).
Reason for additional Setting for Power-Sync: When Couatl is restarted, the GSX Power-Sync behaves accordingly: Jetway and GSX GPU are not reported as connected anymore, so it will signal that Ground Power is not available anymore. Depending on the Situation the Plane will go Cold & Dark. Hence a Setting for Users who don't want that.
Interaction with new default Ground Power Management: As explained above the GSX Synch can override the default Management, but that is also vice versa: the default Management might already report Available before the GSX Sync reports that. It is imaginable that some GSX Users only want to receive Power "through" GSX for added Immersion. If we want to support that, the default Management would need to be disabled when the GSX Power-Sync is enabled. Just a Thought for Discussion - I would leave it as is its proposed. It is likely that there are also Users being like "I have GSX I want that" and then be like "buhu FBW bugged, I don't get Power at Gate!" because they forgot they need to call GSX because they had enabled that. 😅
Some Ideas for future PRs on refactoring/further Commonality:

320: Fuel Management should be moved from js File to Rust with the same behaviour as on the 380. (So no individual desired Variables Tank per Tank. Just one total Target)
EFB: The "bottom" Part of the Fuel Page (Slider, Input, Button, Rate) could then be refactored to be the same on both Airplanes
EFB: The Aircraft-specific Pages are mostly the Outline then (Aircraft graphic, Total/Tank Values) I tried to bring in some Commonality with this PR, but I have unfortunately too little Knowledge on React & Styling nor any understanding of Rust to do this myself properly 😐 (Would absolutely do it if someone from each Domain - React and Rust - would sacrifice to be on my "Speedial" on Discord for Noob Questions :rofl: )

Discord username (if different from GitHub): Fragtality

Testing instructions

Detailed Instructions will follow later! But basically:

GSX Users: Do normal Flights. Check no Interaction is needed for Fuel, Doors and Power.
GSX Users: Test specific Situations like FOB > planned, different Rates, Instant Fuel working with sync enabled
Non-GSX Users: Test if still behaves as expected

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.

Make sure you are signed in to GitHub
Click on the Checks tab on the PR
On the left side, find and click on the PR Build tab
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

flybywiresim / aircraft