docs: update algolia

[shahednasser]

Update algolia to fix issues with highlighting and snippets

[changeset-bot]

⚠️ No Changeset found

Latest commit: 80154d0

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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
api-reference	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am
api-reference-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am
docs-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am
docs-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am
resources-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 19, 2024 7:10am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 19, 2024 7:10am

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
1627328	Triggered	Generic Password	80154d0	integration-tests/http/tests/user/admin/user.spec.ts	View secret
1627328	Triggered	Generic Password	80154d0	integration-tests/http/tests/user/admin/user.spec.ts	View secret
1627328	Triggered	Generic Password	80154d0	integration-tests/http/tests/user/admin/user.spec.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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}