Add a timeout message

[AlexKnauth]

To distinguish between errors where an auto-splitter update took too long, from other errors, such as panics, running out of stack space, etc.

[AlexKnauth]

When testing with an auto-splitter that loops forever printing looping without calling next_tick().await, the logs look like this:

[2024-05-31 20:08:11][Auto Splitter][INFO] looping
[2024-05-31 20:08:11][Auto Splitter][INFO] looping
[2024-05-31 20:08:11][Auto Splitter][INFO] looping
[2024-05-31 20:08:11][Auto Splitter][ERROR] timeout, no update in 5 seconds
[2024-05-31 20:08:11][Auto Splitter][INFO] looping
[2024-05-31 20:08:11][Auto Splitter][ERROR] Unloaded, because the script trapped: error while executing at wasm backtrace:
    0:  0xb6f - <unknown>!<wasm function 17>
    1: 0x79c9 - <unknown>!<wasm function 106>

Caused by:
    wasm trap: interrupt