Upgrade Typesense from 28.0 to 30.x

Previously https://github.com/jquery/infrastructure-puppet/issues/36.

No rush at the moment, but figured I'd write this up while I still have the previous one fresh in mind.

1. Check release notes at https://github.com/typesense/typesense/releases:
   • Look for deprecations or breaking changes that affect any of these repos:
     • https://github.com/jquery/typesense-minibar
     • https://github.com/jquery/jquery-wp-content
     • https://github.com/qunitjs/jekyll-theme-amethyst
     • https://github.com/typesense/typesense-docsearch-scraper/
   • Look for upgrades that raise our downgrade floor. Typsense allows upgrades past many versions at once, but, we'll want to upgrade in steps to pause at any versions before any version that raises the downgrade potential, so that we don't upgrade to a version we can't downgrade back down from.
2. If changes are needed in typesense-minibar:
   • Propose the changes and wait for code review
   • Publish typesense-minibar release
   • Update copy in jquery-wp-content
   • Update copy in jekyll-theme-amethyst (and tag release here, and apply to qunitjs/qunit:/docs
3. To perform each upgrade:
   • create/edit the node-specific Hieradata (example)
   • run sudo run-puppet-agent on the host
   • run sudo systemctl restart typesense-server on the host
   • Test suggestions at https://jquery.com and https://qunitjs.com
4. If we've upgraded to a version that requires a newer docsearch-scraper: https://github.com/typesense/typesense-docsearch-scraper/
   • Update docsearch-scraper everywhere:
     • https://github.com/search?q=org%3Ajquery+typesense%2Fdocsearch-scraper&type=code
     • https://github.com/search?q=org%3Aqunitjs+typesense%2Fdocsearch-scraper&type=code
     • https://github.com/search?q=org%3Ajquery+path%3Adocsearch.config.json&type=code
     • https://github.com/search?q=org%3Aqunitjs+path%3Adocsearch.config.json&type=code
   • Kick off the workflows to re-index the site.
   • Test suggestions at https://jquery.com and https://qunitjs.com
5. Clean up
   • Change the default profile::typesense::version to match, and and remove redundant node-specific Hieradata override.

Start with the Typesense release notes, the linked infrastructure-puppet Hieradata example, and modules/profile/manifests/typesense.pp. Check the listed dependent repositories for breaking changes, downgrade constraints, and docsearch-scraper requirements before planning staged upgrades. Done means the upgrades, dependent releases or updates, re-indexing, suggestion tests, and default-version cleanup are completed.