JIT/AOT MSAN does not set jit-functions as sanitize

**Describe the bug**
In order to trigger MSAN errors a function in LLVM must be marked as sanitizable. Our JIT/AOT code does not do this. Some MSAN issues (such as calling the jit functions with undefined values) will not be caught.

If you add these attributes several tests begin showing msan errors for unclear reasons. It's unclear if the errors are legitimate (msan error message also says some memory is corrupted and it happens in packed API only).

Needs further investigation.