Track timing

[fregante]

• From Investigate delayed execution of bricks in resource-starved browsers pixiebrix-extension#6581 (comment)

We can add meta-data to the message itself to track the time in messenger vs. handler (with send/receipt/etc. timestamps before delegating to the handler

[fregante]

cc @BLoe thoughts?

I think this information can generate further warning logs or events when context crossing takes a while.

log.debug(type, seq, "↘️ received in", getContextName(), {
  sender,
  args,
  wasForwarded: trace.length > 1,
});

if (tooLong) {
	log.warn(type, seq, "↘️ crossed context in", duration);
}

By "context crossing time" I mean:

• the time between a successful runtime.sendMessage and runtime.onMessage callback to be called
• the time between return and the resolution of the last runtime.sendMessage() Promise

This excludes handler execution time and retries, which are not relevant and already visible respectively.

[BLoe]

Yes, I think it does make sense to log when a specific message takes a long time in this case