replace *.io with 301 counterpart

[kheiner]

Updates directus.io links that return 301 redirects to their current directus.com destinations. Replaces community.directus.io with community.directus.com, roadmap.directus.io with roadmap.directus.com, and one directus.io blog link with the directus.com/resources equivalent. Links to telemetry, components, Bluesky, and CDN assets were left unchanged because they do not return 301s.

curl -sI -L "<address>" | grep -E "HTTP/|location:|Location:" with manual verification for each link

• Fixes *.io to *.com #776

• Related to Update Directus domain links #707

• Related Update remaining *.io references to the current *.com domains where possible directus#27948

[vercel]

@kheiner is attempting to deploy a commit to the Directus Team on Vercel.

A member of the Team first needs to authorize it.

[kheiner]

Links to telemetry, components, Bluesky, and CDN assets were left unchanged because they do not return 301s.

In the directus/directus repo there is more details about the telemetry.directus.* and components.directus.* findings. (Short version: I think they're okay to update but I'm not certain that they're okay to update)

Note

locales.directus.io redirects to a third party and there is no such redirection on locales.directus.com but it should probably be implemented as a safeguard for anyone who might not be aware of the *.io domain's history.