Migrate configuration paths to /etc/easyhaproxy and improve health check support in E2E tests

- Refactored HAProxy configuration files, templates, and paths to use `/etc/easyhaproxy` instead of `/etc/haproxy`.
- Updated Dockerfile to generate DH params and placeholder certificates in the new configuration directory.
- Added health check support with timeout to `DockerComposeFixture` in E2E test utilities.
- Adjusted tests, templates, and plugins to use the new `Consts`-based configuration paths.
- Introduced pytest fixtures for environment isolation and temporary directory management.

tests_e2e/static/conf/config-basic.yml

@@ -5,8 +5,8 @@
 #
 # To use:
 # 1. Update the container name and ports to match your setup
-# 2. Place SSL certificate at /certs/haproxy/host1.local.pem
-# 3. Mount this config: -v ./conf/config-basic.yml:/etc/haproxy/static/config.yml
+# 2. Place SSL certificate at /etc/easyhaproxy/certs/haproxy/host1.local.pem
+# 3. Mount this config: -v ./conf/config-basic.yml:/etc/easyhaproxy/static/config.yml
 
 stats:
   username: admin

tests_e2e/static/conf/config-certbot.yml

@@ -15,14 +15,14 @@
 #    EASYHAPROXY_CERTBOT_EMAIL=your-email@example.com
 #
 # 4. Mount this config:
-#    -v ./conf/config-certbot.yml:/etc/haproxy/static/config.yml
+#    -v ./conf/config-certbot.yml:/etc/easyhaproxy/static/config.yml
 #
 # 5. Persist certificates:
-#    -v ./certs/certbot:/certs/certbot
+#    -v ./etc/easyhaproxy/certs/certbot:/etc/easyhaproxy/certs/certbot
 #
 # How it works:
 # - EasyHAProxy requests certificates from Let's Encrypt via HTTP-01 challenge
-# - Certificates are stored in /certs/certbot/
+# - Certificates are stored in /etc/easyhaproxy/certs/certbot/
 # - Certificates auto-renew when needed
 #
 # Note: Let's Encrypt has rate limits. Use staging environment for testing:
@@ -56,7 +56,7 @@ containers:
   # Domain without certbot (uses custom certificate)
   "custom.example.com:80":
     ip: ["custom-app:8080"]
-    # No certbot - expects certificate at /certs/haproxy/custom.example.com.pem
+    # No certbot - expects certificate at /etc/easyhaproxy/certs/haproxy/custom.example.com.pem
 
   # HTTPS Port 443
   # Serves HTTPS traffic with auto-generated certificates
@@ -65,7 +65,7 @@ containers:
     ip: ["webapp:8080"]
     ssl: true
     # Certificate path (auto-generated by certbot)
-    # /certs/certbot/example.com/fullchain.pem
+    # /etc/easyhaproxy/certs/certbot/example.com/fullchain.pem
 
   "app.example.com:443":
     ip: ["app:3000"]
@@ -76,7 +76,7 @@ containers:
     ip: ["custom-app:8080"]
     ssl: true
     # Place your certificate at:
-    # /certs/haproxy/custom.example.com.pem
+    # /etc/easyhaproxy/certs/haproxy/custom.example.com.pem
 
 # Multiple domains with different backends
 # Certbot will request separate certificates for each domain

tests_e2e/static/conf/config-deny-pages.yml

@@ -6,7 +6,7 @@
 #
 # To use:
 # 1. Update container names and ports
-# 2. Mount this config: -v ./conf/config-deny-pages.yml:/etc/haproxy/static/config.yml
+# 2. Mount this config: -v ./conf/config-deny-pages.yml:/etc/easyhaproxy/static/config.yml
 # 3. Test blocked paths:
 #    curl http://host1.local/admin        # Should return 404
 #    curl http://host2.local/wp-admin     # Should return 403 (different config)

tests_e2e/static/conf/config-jwt-validator.yml

@@ -11,11 +11,11 @@
 #    openssl rsa -in jwt_private.pem -pubout -out jwt_pubkey.pem
 #
 # 2. Mount public keys:
-#    -v ./jwt_pubkey.pem:/etc/haproxy/jwt_keys/api_pubkey.pem:ro
-#    -v ./jwt_pubkey2.pem:/etc/haproxy/jwt_keys/admin_pubkey.pem:ro
+#    -v ./jwt_pubkey.pem:/etc/easyhaproxy/jwt_keys/api_pubkey.pem:ro
+#    -v ./jwt_pubkey2.pem:/etc/easyhaproxy/jwt_keys/admin_pubkey.pem:ro
 #
 # 3. Mount this config:
-#    -v ./conf/config-jwt-validator.yml:/etc/haproxy/static/config.yml
+#    -v ./conf/config-jwt-validator.yml:/etc/easyhaproxy/static/config.yml
 #
 # 4. Test:
 #    # Without token - should fail
@@ -42,7 +42,7 @@ containers:
         algorithm: RS256
         issuer: https://auth.example.com/
         audience: https://api.example.com
-        pubkey_path: /etc/haproxy/jwt_keys/api_pubkey.pem
+        pubkey_path: /etc/easyhaproxy/jwt_keys/api_pubkey.pem
 
   # Internal API - validate signature only (no issuer/audience check)
   "internal-api.local:80":
@@ -52,7 +52,7 @@ containers:
       jwt_validator:
         algorithm: RS256
         # No issuer/audience = skip those validations
-        pubkey_path: /etc/haproxy/jwt_keys/api_pubkey.pem
+        pubkey_path: /etc/easyhaproxy/jwt_keys/api_pubkey.pem
 
   # Admin API - different issuer and key
   "admin-api.local:80":
@@ -63,7 +63,7 @@ containers:
         algorithm: RS256
         issuer: https://admin-auth.example.com/
         audience: https://admin.example.com
-        pubkey_path: /etc/haproxy/jwt_keys/admin_pubkey.pem
+        pubkey_path: /etc/easyhaproxy/jwt_keys/admin_pubkey.pem
       deny_pages:
         paths:
           - /internal