Implement Tracing

[grod220]

Given we don't want to use any form of telemetry, debugging user issues sometimes feels like a shot in the dark. One thing that can assist with this is implement opt-in tracing to log (and maybe capture the stack?) as different actions are performed in the extension.

Given straight logging could pollute the user's console, this should be something that requires an explicit opt-in. A potential pattern we could extend is the SCT divergence check that can be enabled by globalThis.ASSERT_ROOT_VALID = true which gets detected in the block processor.

I think there are a few high priority areas where logging could help illuminate issues and give clarity to the lifecycle of the extension:

• Block processing
• Service worker lifecycle (services starting up and initiating)
• RPC requests + responses

We should be mindful that enabling the tracing for debugging does not leak any user data but just console.log actions being taken. Example output:

globalThis.TRACING = true

Requesting block 353213
Decrypting block
Incoming BlockHeightRequest
BlockHeightResponse sent back to client
Service worker services error: XYZ
Service worker restarting services

Should explore libraries that could help with this or handrolling a solution ourselves.