feat: track intercepted URL count (app usage)

[whizzzkid]

Blocked By: https://github.com/ipfs-shipyard/ignite-metrics/issues/103

Using https://github.com/ipfs-shipyard/ignite-metrics like in #1117 implement:

• [x] Track DAU - Daily Active Users (i.e. intercepted URLs > 0)
• [x] Track number of URLs actually resolved by companion, i.e. success rate.
• [ ] Track number of URLs resolved over the public gateway (based on #1125)

Additional Notes:

• To implement number of URLs resolved by companion, we'll need to implement some sort of local storage mechanism because reporting each url resolved and not resolved could be (anecdotally) 10+ requests/second/user which would be a lot. Since we intercept every request and resolve URLs that can be identified resolvable using the local node.
• A simple approach could be to maintain a local counter to be incremented and flush the count every N-hours (using the alarms API).
• Once the values are sent, we can reset the counter and start again.
• This metric will go down as MV3 comes into effect.
• We can store metrics locally and sync periodically within https://github.com/ipfs-shipyard/ignite-metrics

[lidel]

Dropping some other feature usage metrics that would be very valuable:

• more resolution around IPFS page load success/failure rate
  • count root document loads vs subresource loads (a single page can have hundreds of subresources)
  • count the type of content path: immutable /ipfs/cid vs mutable cryptographic /ipns/libp2p-key vs mutable DNSLink /ipns/dnslink-name
• count how many times user clicked on browser-action menu items or context menu on a page (will inform us which type of addres is copied the most, is import to MFS used at all etc)

[BigLep]

Before we write code here, I want to make sure we have clearly defined the metrics we're going to collect and report. I'ld like to review this please when it's ready so save potential churn later.

[SgtPooki]

• what is the avg number of intercepted urls for users who have intercepted IPFS urls
• How many web requests are ipfs urls?

[whizzzkid]

MV3 does not allow this. this was possible in mv2, but mv3 does not want extensions to be touching the requests, just tell the browser what needs to happen and it will do that for you.

I have an issue open with chrome team asking for the stats api, but I don’t think that’s going to happen: https://bugs.chromium.org/p/chromium/issues/detail?id=1429170

In the meantime, we can probably append utm_* params to redirect url, which provides the source as the redirection rule id. Then cross check if the observed request is being redirected because of the rule the extension added. This may lead to reliable detection of redirected requests.