feature(discovery): add Trieve search and AI chat to the docs (old Mintlify functionality)

[skeptrunedev]

We are huge Coolify fans and have been sponsors since June last year. Coolify is an awesome service for our business ❤️ . Trieve provides search and AI chat for all of the Mintlify documentation sites!

Previously, when Coolify's docs were on Mintlify, it had AI chat and search that were heavily used and we wanted to restore the functionality for free to aid the general community!

We deployed a preview of the site at cooldocs.trieve.ai/docs to hopefully make this easier to review.

The functionality works as follows:

1. We load the documentation site into a search index via the trieve-vitepress-adapter CLI package. This is included as a CI action so updates will happen automatically and the search index never falls out of date.
2. We replace the current onClick action of the search input button with a new one that opens the Trieve search box using a client side JS script that loads async. This is minimally invasive and much easier to revert than an installed package that changes which search component gets built into the application wholesale.

Post-merge some secrets will need to be set for CI actions on the repository:

We can send these via a DM on discord or any other platform, cheers!

[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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	21a0a16	docs/public/trieve-user-script.js	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.}

[skeptrunedev]

⚠️ 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
🛠 Guidelines to remediate hardcoded secrets
🦉 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.

This is intentional as it is a specifically permission'ed key meant for public accessibility.