Fix CTD caused by misaligned pointer

[Eathox]

Rust added more debug assertions a while back: in 1.70.0 One of these checks is for misaligned pointers when using slices and arma gives us the command arguments misaligned, resulting in a panic only on debug builds.

This PR fixes that by manually traversing the array and using read_unaligned.

[codecov]

Codecov Report

❌ Patch coverage is 96.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 90.0%. Comparing base (53086c1) to head (3830a3d).

Files with missing lines	Patch %	Lines
arma-rs/src/call_context/stack.rs	87.5%	1 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
arma-rs/src/call_context/call.rs	74.8% <100.0%> (+23.6%)	⬆️
arma-rs/src/command.rs	72.6% <100.0%> (+5.3%)	⬆️
arma-rs/src/lib.rs	97.6% <ø> (+1.8%)	⬆️
arma-rs/src/call_context/stack.rs	96.8% <87.5%> (+96.8%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Eathox]

More testing proofed its still broken, will reopen once I know more

[Eathox]

Command parsing was fine, I just missed call context also being affected.
As part of this I also discovered (and fixed) that steamId and remoteExecutedOwner were being read wrong and gave garbage values.

I've added a test that I believe now covers every instance where this could happen.
As part of this I decided to make RawStackTraceLine and RawContextStackTrace pub but hidden so they could be reused in the emulation test.

Also my testing showed that Arma seems to always sends an count of 6 to RawArmaCallContext::from_arma even when not requesting a stack trace so I would have liked to add a stricter if condition like so:

let flags = FeatureFlags::from_bits(unsafe { RVExtensionFeatureFlags });
let call_stack = if count > 5 && flags.context_stack_trace() {

However the emulation test I added is a little awkward as I didn't figure a way for it to request the context like arma does so instead it uses handle_call_context and the bool clear_call_context in handle_call to make sure it stays around. Which sadly means that flag wont be set in time.

[Eathox]

Nightly/Miri update introduced a bug? parse_exponential just fails now no matter what commit I checkout