Remove duplicate links from the header and footer

The footer repeated links the page already has: Document (the header),
Reference, Plugins and the full reference (pages of the documentation),
the release notes (the home page) and Source (the GitHub icon in the
header). Their column and the Source link are gone; the footer keeps the
Tala family (Tala, Talac, ViGet) and progmasoft.com, which no other part
of the site links. The labels only those links used are removed from the
four languages. Tests, nuxt typecheck, Prettier and nuxt generate pass.

nuxt generate creates dist as a symbolic link to .output/public. The
"dist/" pattern matches only a directory, so the link was committed with the
previous change; it is removed from the index and the pattern now matches
the link too.

Reference and Plugins led to pages of the documentation the Document link
already reaches, and Releases to the GitHub releases, so the header (desktop
and mobile menu) now holds the Document link alone, current on every
/docs page. The unused "releases" label is gone from all four languages.
The footer keeps its links. Tests, nuxt typecheck, Prettier and nuxt
generate pass; the generated header reads Document, Dokument, Документ and
מסמך.

The documentation link now reads "Dokument" in de-DE, "Документ" in ru-RU
and "מסמך" in he-IL, matching "Document" in en-US. Only the labels change;
the link still goes to /docs/... in every language. Tests, nuxt typecheck
and Prettier pass.

The en-US header link to the documentation read "Docs"; it now reads
"Document". The German, Russian and Hebrew labels are unchanged. Tests,
nuxt typecheck and Prettier pass.

Take minimatch and glob past their advisories

minimatch 10.2.6 (CVE-2026-118764, denial of service through globparts
amplification) and glob 13.0.6 (CVE-2026-118773, traversal after an
AbortSignal timeout) reach the site through @nuxt/content, nitropack and
c8, whose ranges have not moved. Overrides take them to minimatch 11.0.5
and glob 14.0.4. Both run only while the site is generated, on the files
of this repository, so no visitor could reach them; the override clears
the alerts without waiting for the upstream ranges.

zod 3.25.76 and deepmerge 4.3.1 keep their alerts. Nuxt Content checks
the collections of this repository with zod, and rollup merges its own
options with deepmerge, both at generation time on input from this
repository; zod has no fixed 3.x and deepmerge no fixed release, and
npm's way out is to go back to @nuxt/content 2 and nuxt 4.1.

Show how a plugin build finds the Gradle plugin of Tazel 0.4.0.3

The settings of the plugin example listed the Gradle Plugin Portal first
and filtered only the Progmasoft repository, so Gradle asked the Portal for
com.progmasoft.tazel.plugin before Progmasoft's own repository. The
example now makes https://maven.progmasoft.com/tazel exclusive for
com.progmasoft.tazel and its subgroups: Gradle resolves those there and
nowhere else, and every other plugin from the Portal.

The example builds as written: the Gradle plugin and tazel-api resolve
and jar writes the plugin JAR with its descriptor.