fix: do not panic when encountering unkown enum values in gsx integration

[Saschl]

Fixes #[issue_no]

Summary of Changes

For some LVARs, GSX seems to set an unkown value when using the "Complete Now" functionality. Instead of panicking and crashing the whole wasm gauge, we now log a warning and return a fallback value.

Also adds a custom hook for panics to print the error message. The default behaviour does not print the backtrace anymore, which makes troubleshooting harder as we get not much information in the logs besides the info that the gauge crashed.

Screenshots (if necessary)

New log when the wasm panics

References

Additional context

Discord username (if different from GitHub):

Testing instructions

GSX needed:

1. Enable GSX sync in the EFB and load a flight plan or enter some values on the weight/balance page.
2. Start boarding with GSX
3. A few moments after, complete the boarding early via the GSX menu (clicking on the "boarding" tile again -> Complete now)
4. Make sure the plane still works (powers up, flaps lever and parking brake lever work)

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 or flybywire-aircraft-a380-842 download link at the bottom of the page

[Saschl]

I'd also like to print to stderr but the formatting in the console is off then as it prints multiple lines. Like this the offending line is printed in the same log line which makes search easier

[beheh]

How about we change to the TryFrom trait here instead? That forces the consumer to deal with this (because then the conversion can Err), rather than hiding behind a panic in the enum.