fix(webapp): Invalidate cache on deleting integrations and adding connection from integration page

[nalanj]

I noticed a couple of places where the connection list cache wasn't being correctly invalidated:

1. When creating a new connection from the integrations page (like right after creating a new integration).
2. When deleting an integration.

How I Tested This

1. Go to Connections so the cache is warmed up
2. Create a new Unauthenticated Integration
3. Create a new connection for the new Unauthenticated integration
4. Return to Connections. The new connection should be in the list.
5. Go back to the new integration, go to the settings tab, and delete it.
6. Go back to connections. The new connection should now be gone.

[bodinsamuel]

🧹 💨

[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
8205899	Triggered	Generic Password	dd2465b	packages/database/lib/getDbConfig.ts	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.}