Read every setting through viper and rename the settings (closes #211)

Every setting of waf and rproxy is read through viper, in place of the
os.LookupEnv function Main passed down. NewViper turns AutomaticEnv and
AllowEmptyEnv on, so a setting that is set but empty reads as set. A
setting may also be given as a file, the _FILE form, which rproxy's
settings now have too; rproxy still writes nothing to disk.

The settings are renamed: waf's take the prefix SWW_WAF_, rproxy's take
SWW_RPROXY_, and the shared SWW_COMMAND keeps SWW_. The Core Rule Set's
settings take SWW_WAF_CORE_RULE_SET_ rather than SWW_WAF_WAF_.

Model: deepseek-v4-pro (first version); opus-5-5 (rework)

internal/coreruleset/ghost.conf

@@ -3,7 +3,7 @@
 # rules it switches off, so this file is loaded before the Core Rule Set's
 # rules. Each comment names a request a rule refused. An exclusion on a field of
 # a body applies only when the query has no parameter of that name, so it
-# matters only while SWW_WAF_BODY_LIMIT is set.
+# matters only while SWW_WAF_CORE_RULE_SET_BODY_LIMIT is set.
 #
 # Ghost's admin and its integrations call the Admin API under /ghost/api/admin/,
 # themes and Ghost's own scripts call the Content API under /ghost/api/content/,
@@ -11,7 +11,7 @@
 # path, so the title of the first post saved is json.posts.0.title.
 
 # Every rule below is skipped unless Inspect has set tx.app_ghost. It sets it
-# while SWW_APPS is unset, or lists ghost for the request's hostname.
+# while SWW_WAF_APPS is unset, or lists ghost for the request's hostname.
 # The skip reaches only phase 1, so a rule of a later phase must check
 # tx.app_ghost itself.
 SecRule &TX:app_ghost "@eq 0" \