[Tests] Periodically run Firecracker integration tests under sanitizers

[raduiliescu]

[acatangiu]

This is now unblocked after merging #2599

[dianpopa]

Also addresses #119

[roypat]

I'm marking this as parked, as generally, being able to detect memory leaks and undefined behavior in our integration tests would be nice to have, albeit significantly less relevant due to Rust's strong memory safety guarantees (and for those parts of the codebase we have covered with kani harnesses, we get these guarantees from kani). Furthermore, Valgrind does not seem to play nicely with Rust code, as rustc's LLVM backend on x86_64 uses a lot of instructions which valgrind does not support (for example, the SIP hasher used by default in Rust's HashMap and HashSet uses hardware acceleration not supported by valgrind).