DSLX: trace! messages from the JIT are returned in an unpredictable order

In the interpreter, trace messages are emitted in the expected order

In the JIT, though, they come out in an unexpected ordering - even in the unopt output.

i.e., if you have
```
let _ = trace!("A");
let _ = trace!("B");
let _ = trace!("C");
```

They messages may be present in the returned InterpreterResult::events vector in B, C, A, or any other order, as far as I can tell. Order matters!