fix: patch module based on reports from iniBuilds A350 launch

[SkySails]

This pull request includes several changes across different files to improve error handling, add new enum variants, and enhance initialization logic. The most important changes are grouped by theme below.

Error Handling Improvements:

• src/database/src/database.rs: Changed the handling of ValueRef::Blob to return None instead of panicking.
• src/database/src/output/airspace.rs: Updated impl Path to use unwrap_or_default for coordinates and handle invalid path types gracefully. [1] [2]
• src/database/src/output/fix.rs: Modified impl Fix to return FixType::None instead of panicking for unexpected table values.
• src/database/src/output/procedure_leg.rs: Updated impl From<sql_structs::Procedures> for ProcedureLeg to use unwrap_or_default and provide default values for missing data. [1] [2] [3]

Enum Enhancements:

• src/database/src/enums.rs: Added new variants Either to TurnDirection and Paved to RunwaySurface. [1] [2]
• src/database/src/output/airspace.rs: Added Unknown variant to PathType.

Initialization and Update Logic:

• src/wasm/src/dispatcher.rs: Introduced first_update flag in Dispatcher to handle initialization on the first update and adjusted delta_time initialization. [1] [2] [3]

Utility Function Improvements:

• src/wasm/src/util.rs: Enhanced file handling functions to check for empty file names more safely. [1] [2]

SIMDEV-350

[professoralex13]

I'm not a huge fan of unwrap_or_default in all these cases, could we instead just have graceful failure without a panic using Result? If all these values default to zero in failure cases, surely that makes it harder for the user application to tell what is invalid data and what is actually just (0, 0) coordinates? same goes for the other unwrap_or_default I didn't highlight

[SkySails]

AFAIK this approach was taken in order not to break iniBuilds current implementation, which we assume is not ready to handle a change in behavior like that. Let's discuss it!