Unit tests have confusing behaviour on headless systems

### Describe the bug

Running the unit tests on a headless system (CI) or via an ssh connection can be quite confusing if an assertion is triggered. The current behaviour is that the test is aborted without any output, which makes it really hard to distinguish from a successful run. It also swallows important diagnostic information such as the assertion and file and line number.

CI works around this by setting EBPF_ENABLE_WER_REPORT, which is not documented anywhere. Users / developers of the runtime need to discover this flag and ensure it is set everywhere (for example by adding it to $PROFILE).

### OS information

_No response_

### Steps taken to reproduce bug

1. Write unit test which triggers an ebpf_assert
2. Run test
3. Observe output

### Expected behavior

Failed assertions should always be emitted to stderr and not require an environment variable.

### Actual outcome

No output.

### Additional details

_No response_