Drop Xide from the IDE answer of the Overview FAQ

Xide is no longer developed as of 2026-11-08 (Progmasoft/xide#29), so
the answer to "Does Tala require a particular IDE?" no longer calls it a
future interface. In all four languages the answer now says only that
the supported workflow uses command-line tools on Windows, macOS and
Linux.

Let Cloudflare Web Analytics run on the Tala sites

Redirect tazel.tala.run to tazel.net for good

The four hosts of the site now allow Cloudflare's Web Analytics beacon,
but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every
script an intermediary adds. Both now name the beacon, where it loads
from and where it reports, and keep the forum placeholder's same-origin
policy apart.

Cloudflare adds its Web Analytics beacon to each page it serves. The
policies of tala.run, talac.tala.run, talafmt.tala.run and
talalint.tala.run fell back to default-src 'self' for scripts, so the
browser refused the beacon. They now allow scripts from
static.cloudflareinsights.com and connections to cloudflareinsights.com;
the beacon reports to /cdn-cgi/rum on the same host.

The integrity tests still expected tazel.tala.run to serve the Vue build
with its own robots.txt and sitemap.xml. They now count four app-shell
hosts and check the redirect itself: the two former pages go to their
pages under tazel.net/docs/reference/ with the query string, other docs
paths to tazel.net/docs, everything else to the same path, the /docs/
prefix is a plain one so the regular expression is reached, and HSTS
stays.

OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent
redirect instead of a documentation site.

Tazel has its own site at tazel.net, so tazel.tala.run no longer serves
the build system's pages from this build. Every request answers with a
permanent 308 redirect:

- /docs/commands and /docs/project-file go to their pages under
  tazel.net/docs/reference/, keeping the query string;
- any other page under /docs/ goes to tazel.net/docs;
- every other path goes to the same path on tazel.net.

The host keeps its HSTS header. The README and the comments of the
configuration name the four sites the build still serves.

Say what -- and s(...) do in Tazel custom commands