docs: stop publishing internal references to a public wiki

docs/ is excluded from the code bundle and its scrub gate, because it goes to
the GitHub wiki instead - via a generator that has no gate at all. So the one
part of the repository written in prose, by people, about internal
infrastructure, was the one part nothing checked.

What was reaching a public wiki: the internal git server's URL and hostname,
.gitea workflow paths, developer home directories in the GE-Enforce cutover
reference, and a dev database root password inside a copy-pasteable command in
the import guide.

All replaced with neutral equivalents. tests/test_docs_publishable.py is now the
gate, at the source, in CI - a wiki page cannot be un-published, so catching this
after the fact is not good enough.

PROJECT-REVIEW.md also referred to internal tooling by name throughout; those
references are generalised. It remains an internal candid assessment of this
project that is nonetheless published, which is worth a separate decision.

docs/DEPLOY.md

@@ -7,12 +7,12 @@ shopdb-flask is single-tenant per ADR-004. Each adopting facility runs its own s
 - Docker 24+ and Docker Compose v2 (or equivalent container runtime)
 - A reverse proxy with TLS termination (nginx, traefik, Caddy, GE corporate LB) -- the framework does not terminate TLS itself
 - A MySQL backup destination (offsite recommended)
-- Access to the GE Aerospace Gitea or a clone of the repo
+- Access to the internal GE Aerospace git server, or a clone of the repo
 
 ## Step 1: Clone and configure
 
 ```bash
-git clone https://gitea.proudtech.net/ge-aerospace/shopdb-flask.git
+git clone <internal-git-server>/ge-aerospace/shopdb-flask.git
 cd shopdb-flask
 cp .env.example .env
 ```