bug: running with `--vtune` causes a crash

### Test Case

```
(module)
```

### Steps to Reproduce

```
wasmtime --vtune /tmp/empty.wat
```

### Expected Results

Adding the `--vtune` flag, which enables VTune profiling, should succeed regardless of the environment.

### Actual Results

A snippet of the backtrace:

```
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: error when notifying event', crates/jit/src/profiling/vtune.rs:60:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }', crates/jit/src/profiling/vtune.rs:47:27
...
17: 0x564e6a13571c - ::drop::ha421249d00e9da25
at /.../wasmtime/src/crates/jit/src/profiling/vtune.rs:47:9
18: 0x564e6935d677 - core::ptr::drop_in_place::h4021027fefeb76a5
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ptr/mod.rs:490:1
19: 0x564e6935f22d - core::ptr::drop_in_place>::h3e6586f99c95bc40
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ptr/mod.rs:490:1
20: 0x564e6935c24c - core::ptr::drop_in_place::hb7a0d51da9c6653e
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ptr/mod.rs:490:1
21: 0x564e693b2b64 - alloc::sync::Arc::drop_slow::h6c0d38bb7bee604c
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/sync.rs:1114:18
22: 0x564e6935f9fb - as core::ops::drop::Drop>::drop::haeb7e9ee9f329b2a
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/sync.rs:1711:13
23: 0x564e6935e00b - core::ptr::drop_in_place>::h4fab3897c40d1cc6
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ptr/mod.rs:490:1
24: 0x564e6935bb9b - core::ptr::drop_in_place::h804e987e96a87bb3
at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ptr/mod.rs:490:1
25: 0x564e68f55ce4 - wasmtime_cli::commands::run::RunCommand::execute::h6e097e3761430deb
at /.../wasmtime/src/src/commands/run.rs:230:5
26: 0x564e68dcb405 - wasmtime::Wasmtime::execute::hc576e9eb67754303
at /.../wasmtime/src/src/bin/wasmtime.rs:52:29
```

### Versions and Environment

Wasmtime version or commit: `main`

Operating system: Fedora

Architecture: x86_64

### Extra Info

I thought that perhaps the issue was that Wasmtime expected to be run by VTune. When I try the following, things seem to almost work:

```
rm -rf /tmp/vtune-results
vtune -collect hotspots -result-dir /tmp/vtune-results target/debug/wasmtime --vtune /tmp/empty.wat
```

I do see a worrying line in the output, though: "vtune: Error: Cannot load data file `/tmp/vtune-results/data.0/40123-40133.0.trace' (Data file is corrupted)." But I can replicate the original bug when I use a more complex WAT file:

```
rm -rf /tmp/vtune-results
vtune -collect hotspots -result-dir /tmp/vtune-results target/debug/wasmtime --vtune ~/Code/wasmtime/tests/all/cli_tests/simple.wat
```