Add HTML redirects for legacy How Do I pages

[shai-almog]

Motivation

• Fix broken legacy root-level "How Do I" pages that still serve the old stand-alone URLs by forwarding them to the canonical /how-do-i/... article locations.
• Apply lightweight HTML redirects in the content files to avoid touching the site-wide redirect rules which are sensitive.

Description

• Replaced the body of docs/website/content/create-an-ios-provisioning-profile.md with an HTML redirect that preserves the frontmatter and adds a meta refresh, a canonical link, a JavaScript window.location.replace fallback, and a user-facing anchor fallback pointing to /how-do-i/how-do-i-create-an-ios-provisioning-profile/.
• Replaced the body of docs/website/content/take-a-picture-with-the-camera.md with the same HTML redirect pattern pointing to /how-do-i/how-do-i-take-a-picture-with-the-camera/.
• The redirects use meta http-equiv="refresh" for automatic forwarding, a link rel="canonical" to the new URL, and a small HTML body that links to the target for clients without automatic redirect support.

Testing

• Located legacy root-level how-do-i pages using the repository scan (python script that checks docs/website/content/*.md for type=howdoi) and confirmed two affected files were found.
• Verified the updated files contain the redirect markers with rg -n "meta http-equiv=\"refresh\"|window.location.replace|This page moved to" and confirmed presence of meta refresh, JavaScript redirect, and fallback link in both files.
• Attempted to run the static site build with hugo --panicOnWarning but hugo was not available in the environment, so the generated site could not be validated here.

---

Codex Task

[github-actions]

Cloudflare Preview

• URL: https://pr-4621-website-preview.codenameone.pages.dev
• Branch: pr-4621-website-preview