Add initial ETW support to Rust SDK and HelloWorld sample

[Branden Bonaby (bbonaby)]

Why is this change needed?

The change Introduces end-to-end ETW (TraceLogging) support for VBS enclaves in our sdk.

What changed?

• Added ETW support to the Rust SDK using the tracelogging crate.
• Implemented enclave-side ETW forwarding logic and host-side ETW plumbing via new EDL definitions and generated bindings.
• Introduced SDK helpers to register and unregister ETW providers and callbacks.
• Updated the HelloWorld Rust sample to emit ETW events from inside the enclave.
• etw.md describing enclave and host integration patterns and how developers can use the SDK + tracelogging crate to write events..
• Extended codegen script to support EDL import directories.
• Ensured all generated Rust ABI structs use #[repr(C)] for ABI correctness.
• In the enclave.rs in the host sdk I realized we were using only the debug flag for enclave creation. I updated the create_and_initialize and create_and_initialize_with_threads api's to now accept a flag value so they can be created for production builds, where enclave debuggability is not acceptable.

How was this tested?

• Built and ran the updated HelloWorld sample end-to-end, verifying enclave load, ETW provider registration, event emission, and clean teardown.
• Validated that ETW callbacks are correctly forwarded from the host into the enclave.
• Confirmed generated code compiles for both host and enclave targets with updated codegen scripts.
• Confirmed userbound key sample still works after updates.

End-to-End dataflow

Enclave (VTL1)
  write_event!()
      ↓
SDK enclave ETW intercept
      ↓
ABI passthrough
      ↓
Host ETW bridge (EventWriteTransfer)
      ↓
Windows ETW 

Demo

Enclave-trace-logging-demo.mp4

[Branden Bonaby (bbonaby)]

This conflicts with #187 so will let that one go in first and then first/update things with my branch after.

[Soham Das (SohamDas2021)]