Remove what is about deploying behind Gitea (closes #209)

Delete the Gitea compose setup, its document, its two scripts and their
make targets. Documents and tests no longer use Gitea as the example
deployment. The Core Rule Set exclusions for Gitea's false positives in
internal/waf stay, with their comments and tests.

Model: opus-5-5

README.md

@@ -338,8 +338,8 @@ full, and the limits that are fixed rather than settings.
 Each example is a complete `compose.yaml`. `smallwebwaf` is the tag
 `make docker` gives the image; on another host, use the name you pushed it
 under, by digest. Docker Compose puts the services on a private network of its
-own, where each reaches the others by service name. Each example publishes
-`rproxy`'s port on the host, for trying it out.
+own, where each reaches the others by service name. Each publishes `rproxy`'s
+port on the host, for trying it out.
 
 ### Smallest setup
 

SPEC.md

@@ -866,9 +866,12 @@ and the default file.
   of a code forge, `/.env` is a probe, while
   `/<owner>/<repo>/src/branch/main/.env.example` is a file in a repository that
   any visitor may open. Anchor the paths of your own `ban` rules at the site
-  root too. A rule has one target, so a `path` rule applies on every site behind
-  that `servewaf`. A directory mounted over `SWWAF_RULES_DIR` replaces the
-  default file; single files mounted into it add to it.
+  root too. Anything else, such as a rule banning WordPress probes in front of
+  an app that is not WordPress, belongs in a file the deployer adds to the image
+  `servewaf` runs from, or mounts. A rule has one target, so a `path` rule
+  applies on every site behind that `servewaf`. A directory mounted over
+  `SWWAF_RULES_DIR` replaces the default file; single files mounted into it add
+  to it.
 - Rules meant to be edited while `servewaf` runs belong in a mounted directory,
   not a mounted file. Many editors save a file by replacing it, and a container
   keeps seeing the old one when the file alone is mounted. The lookup database