feat: support detailed server timings

[achingbrain]

When the withServerTimings option is true, report detailed timings - e.g. how long to find providers, how long to connect to them, to download blocks, etc.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[achingbrain]

Depends on:

• fix: detect http/https addresses with paths and optional ports multiformats/js-multiaddr-matcher#67
• feat: emit standardized block broker events helia#995

[achingbrain]

Fixes ipfs/service-worker-gateway#956

cc @dennis-tra

[github-actions]

🎉 This PR is included in version @helia/verified-fetch-v7.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version @helia/verified-fetch-interop-v4.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[dennis-tra]

Thanks @achingbrain, it should automatically appear in our database. I'll monitor the data

[achingbrain]

No problem - it'll need a service worker gateway release before the headers start to appear. This should happen later today.

[achingbrain]

This has been deployed on inbrowser.link now so please give it a go.

N.b. the server timing values are heavily abbreviated to reduce the header size, everything should be documented in the readme but let me know if anything doesn't make sense.

[dennis-tra]

Nice, the data is there! Here's one random probe

{"b":0.013,"c":1.255,"f":1.2770000000000001,"i":"0","p":0.001}

Edit: Ah I see that e.g., p can appear multiple times. If I'm not mistaken I'm filling a map and thus overwrite earlier values. Need to double check

[achingbrain]

Please check the tables in the README.

p is a provider, and you can find multiple providers for a given block so yes, it can appear multiple times.

If you inspect the desc field of the timing tuple, it will tell you the first 10 chars of the PeerID of the provider, and the routing system that found it.