Bring the Tazel pages up to date

Pin glob and minimatch below c8 past their advisories

The latest c8 still asks test-exclude for ranges that npm audit now
reports, and the fix npm offers moves c8 back a major version. Overrides
take the fixed releases instead; coverage works with them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

They said version 0.1.0 is built with the compiler of Tala 0.1.0, which
stopped being true with the next release of each. What holds for every
version is that a tool accepts what its compiler accepts.

Test suites work, so the note no longer lists them. The commands page
adds fetch, custom, the build cache, remote serve and the daemon, with
sections on spending the machine and on custom commands. The project
file page adds the execution block, the size levels and the shape of a
version. All four languages.

Add the talafmt.tala.run and talalint.tala.run sites

The build that serves tala.run, talac.tala.run and tazel.tala.run now
also serves the formatter and the linter, chosen by host name like the
others. Each site has a landing page and two documentation pages in
en-US, de-DE, ru-RU and he-IL:

- talafmt: the command line (inputs, --check, --emit, exit status 2 for
  an unreadable line) and what it changes (indentation, line endings,
  trailing whitespace, the final newline; protected text; encodings from
  talafmt.kts).
- talalint: the command line (--fix) and what it checks: the compiler's
  diagnostics as compiler.<code>, and format.trailingWhitespace,
  format.mixedLineEndings and format.missingFinalNewline. --fix rewrites a
  file with talafmt's default layout, which also re-indents blocks.

The facts follow the READMEs of Progmasoft/talafmt and Progmasoft/talalint
0.1.0 and the talalint source. site.ts lists the sites once, with their
names, so the header, the landing page and the documentation shell no
longer keep their own copies. Each host has its robots.txt and
sitemap.xml, nginx gains the two server blocks, and the tests check the
new hosts like the others.