Remove error analytics

[nop33]

I want to avoid the issue of floading the analytics with errors because of a useEffect, like it happened with the GH API rate limits. I went through both our wallets in search of the places we report things to PostHog and removed some. @mvaivre I would like to review them with you and think of a way to ensure that we won't end up with the same problem in the future.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a41c987

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mvaivre]

Should we plan a little call to go through this?

[nop33]

Yes

[nop33]

@mvaivre as we are preparing to fix the analytics issue, I would like to merge this so I am requesting your review. As the description of the PR says, I went through all places where we call the Posthog API to see where there could be a potential issue in the future. I removed a few API requests in places that I deemed necessary.

I also posted a question in Posthog support here: https://posthog.com/questions/how-to-limit-the-amount-of-requests-sent-from-my-app-to-posthog

This issue is related: #453

Let me know how you'd like to proceed.

[nop33]

@mvaivre when you have the time, please check my last comment here 🙏

[nop33]

kind ping @mvaivre for my previous comments 🙏

[mvaivre]

😨 you're right. I wanted to start counting from -1 to make it less obvious, but apparently I considered this as non vital and made a mistake 🙃