fix: don't set PARANOIA by default as if conflicts with the other vars

When `PARANOIA` and `BLOCKING_PARANOIA` are both set but
`DETECTION_PARANOIA` isn't, the detection paranoia level may be set to a
value smaller than the blocking paranoia, which triggers a rule that
checks for this situation. Since `PARANOIA` is deprecated, simply don't
set it by default.

README.md

@@ -119,7 +119,7 @@ You can achieve the same results just by getting any version you want, and using
 git clone https://github.com/coreruleset/coreruleset.git myrules
 cd myrules
 git checkout ac2a0d1
-docker run -p 8080:8080 -ti -e PARANOIA=4 -v rules:/opt/owasp-crs/rules:ro --rm owasp/modsecurity-crs
+docker run -p 8080:8080 -ti -e BLOCKING_PARANOIA=4 -v rules:/opt/owasp-crs/rules:ro --rm owasp/modsecurity-crs
 ```
 
 ## Quick reference
@@ -412,8 +412,8 @@ docker run \
    -e MODSEC_AUDIT_LOG=/var/log/modsec_audit.log \
    -e LOGLEVEL=warn \
    -e ERRORLOG=/var/log/modsec_error.log \
-   -e PARANOIA=1 \
-   -e EXECUTING_PARANOIA=2 \
+   -e BLOCKING_PARANOIA=2 \
+   -e DETECTION_PARANOIA=2 \
    -e ENFORCE_BODYPROC_URLENCODED=1 \
    -e ANOMALY_INBOUND=10 \
    -e ANOMALY_OUTBOUND=5 \

apache/Dockerfile

@@ -146,7 +146,6 @@ ENV \
     TIMEOUT=60 \
     WORKER_CONNECTIONS=400 \
     # CRS specific variables
-    PARANOIA=1 \
     ANOMALY_INBOUND=5 \
     ANOMALY_OUTBOUND=4 \
     BLOCKING_PARANOIA=1

apache/Dockerfile-alpine

@@ -156,7 +156,6 @@ ENV \
     TIMEOUT=60 \
     WORKER_CONNECTIONS=400 \
     # CRS specific variables
-    PARANOIA=1 \
     ANOMALY_INBOUND=5 \
     ANOMALY_OUTBOUND=4 \
     BLOCKING_PARANOIA=1

nginx/Dockerfile-alpine

@@ -203,7 +203,6 @@ ENV \
     SSL_VERIFY=off \
     WORKER_CONNECTIONS=1024 \
     # CRS specific variables
-    PARANOIA=1 \
     ANOMALY_INBOUND=5 \
     ANOMALY_OUTBOUND=4 \
     BLOCKING_PARANOIA=1