Restructure Docs - Stage 4a (#2280)

* create Develop and Deploy tabs; move Operations; re-weight pages

* move capacity planning page; create section dropdown content

* added aliases to frontmatter

* update link references to new canonical links; maintain anchoring

* address remaining link issues and errors

* fix outlier tutorial reference issue

* Treat 'develop' and 'deploy' as a unified search space

* fix some frontmatter aliases

* add section header redirects

* fix 'Operations' redirect to go to 'Deploy' tab

* update redirects file for * pattern

* add :splat to redirect references

* Add wildcard to each entry in _redirects file

---------

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

qdrant-landing/content/blog/cve-2024-3829-response.md

@@ -45,13 +45,13 @@ guide](https://qdrant.tech/documentation/cloud/quickstart-cloud/#step-2-test-clu
 If your Qdrant deployment is local, you do not need an API key.
 
 Your next step depends on how you installed Qdrant. For details, read the
-[Qdrant Installation](https://qdrant.tech/documentation/operations/installation/)
+[Qdrant Installation](https://qdrant.tech/documentation/installation/)
 guide.
 
 #### If you use the Qdrant container or binary
 
 Upgrade your deployment. Run the commands in the applicable section of the
-[Qdrant Installation](https://qdrant.tech/documentation/operations/installation/)
+[Qdrant Installation](https://qdrant.tech/documentation/installation/)
 guide. The default commands automatically pull the latest version of Qdrant.
 
 #### If you use the Qdrant helm chart