feat: measure amount of running instances

[Matvey-Kuk]

• Reverting fix(startup): posthog issue when enabled and no connectivity #631
• Not reporting to posthog if there is no connectivity to it.
• Tested with air-gapped keep.
• Removing duplicate env var: ENABLE_POSTHOG_API because we have DISABLE_POSTHOG
• Reporting backend uptime to PostHog every 10 minutes.
• PostHog is messing up with unnittests causing infinite recursion. Spent a pile of time trying to find the reason, just disabling it for Unittests.

Closes #2367

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
keep	⬜️ Ignored (Inspect)	Visit Preview		Nov 3, 2024 1:39pm

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8134198	Triggered	Generic High Entropy Secret	ba20a40	keep-ui/app/frigade-provider.tsx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[talboren]

some small comments

[talboren]

LGTM