Move guides to new section

[Strift]

Why

Move cookbooks, deployment, and front-end pages from Learn to Guides top-level section.

How

• Move MDX files to the guides folder
• Update the sidebar-config.json configuration file
• Update links in existing pages
• Update redirects.json to exhaustively list all updated URLs
• Update link checker script to test against sidebar-config.json configuration too

⚠️ Checks are currently failing for all guides/* URLs

Deployment

This PR needs to be merged before the website's PR that enables the guides section.

This will allow us to get the following deployment process:

1. The website will trigger a deployment: the content moved to Guides will be temporarily inaccessible (but the site won't break)
2. Merge the website PR to trigger a deployment: the Guides section will be activated and its content will be activated

[meili-bot]

How to see the preview of this PR?

⚠️ Private link, only accessible to Meilisearch employees.

Go to this URL: https://website-git-deploy-preview-mei-16-meili.vercel.app/docs/branch:add-guides-section

Credentials to access the page are in the company's password manager as "Docs deploy preview".

[CaroFG]

Hey, am I supposed to be able to see the Guides section in the preview? Because it does not appear

[guimachiavelli]

If this is purely a draft and not yet intended to be merged, can I convert it to a draft PR?

[Strift]

@guimachiavelli Apologies, I converted it to a draft PR ✅

---

@CaroFG Link preview doesn't work, because this requires toggling something in website repository (see related changes)

You can preview changes with this link: https://website-git-feat-enable-docs-guides-meili.vercel.app/docs

[CaroFG]

Ok, LGTM but at some point we will need to consider organizing the guides by themes into subsections

[guimachiavelli]

Two main things:

1. I'm a bit concerned about the added line to the workflow file. Wouldn't want to mess up our already frail pipeline. I'm terrible with GH actions and etc, so do ping clémentine if you need help assessing this
2. The broken links action is failing. Might be related to the previous item

The rest is fairly minor, mostly due diligence

[Strift]

Thanks for the reviews.

@guimachiavelli I think the action is failing because GitHub is running the action code that is on the main branch. If you take a look, you can see that only the links to /guides URLs are failing.

That's because this PR also contains the relevant changes in the GitHub action to validate links to guides.

It's a bit more work, but if you prefer, I can move those changes to another PR, so we can:

1. Merge the PR that updates the action
2. Relaunch CI for this PR with the updated action

What do you think?

[Strift]

I moved the changes related to CI in #2841.

If we merge that one first, the CI will pass on this PR.

[CaroFG]

lgtm!

[guimachiavelli]

LGTM