fix: Handle metrics breakage issue in mv3

[SgtPooki]

From @whizzzkid:

We might need to revisit/refactor ignite-metrics, because mv3 removes the background_page context and replaces it with service-wroker context, i.e. reporting metrics from the background would be the same constraint as if running from within a service worker.

Metrics might break on ipfs-companion, because countly sdk needs window context and mv3 replaces background page with a service-worker context, i.e. no more countly:

• Webpack has been incapable so far of producing an asset free of window references.
• counly-sdk-node has a broken package which does not allow node projects to build, but the team’s advice is to move to the web sdk 🤦🏼  Can't resolve 'cluster' in '/projecta/node_modules/countly-sdk-nodejs/lib' Countly/countly-sdk-nodejs#8
• Another alternative could be injecting countly on every page where metrics need tracking (ugh)

Discussed at:

• Nishant daily update: https://filecoinproject.slack.com/archives/C03KQ8MC62Y/p1677703254599349
• IP Stewards sitrep: https://www.notion.so/pl-strflt/2023-03-03-IP-Stewards-SitRep-d286014bfc3b4aef8da7750db2e696da?pvs=4#ebbdd84aeae048c6844ab28a84b2474d

[SgtPooki]

FYI: webpack has functionality to replace text during builds via the define plugin: https://webpack.js.org/plugins/define-plugin/#usage

This may help, though it would require us to rebuild our own countly sdk. We could also use patch-package, but ideally countly would produce a decent SDK that could be consumed in multiple environments.

[whizzzkid]

Being tracked in #1169

[BigLep]

@whizzzkid : what was the verdict here?

[whizzzkid]

@BigLep This issue is being tracked in #1169 as this is a blocker for that. So this is essentially a duplicate issue.