This allows sites using redirect=proxy to still generate ACME
certificates by not passing the acme requests through to the proxy.

We should also consider using this for other features available such as
own error documents, SSI and custom directives.

We sometimes had one and mostly had two capture groups. Now we always have two capture groups and thus can always use $2 for the redirect target.

Fixes #6144

This reverts commit 0d61c249

This reverts merge request !1033

Change the name from proxy_protocol to use_proxy_protocol in vhost file due to site level overriding the check

tested both on apache2 and nginx with haproxy load balancer on TCP Mode

Added Global Setting to Server config tab to
  - Enable & Disable the feature
  - Set the Proxy HTTP & HTTPS Ports

Added Per site level switch to enable and disable feature (Located in the Web Tab under the advanced section)

Added Apache2 and Nginx vhost updates to enable proxy_protocol on the listen lines

Added New database column to web_domain called "proxy_protocol" to enable site level config (Patch file Added upd_0089.sql)

Updated the Base Table SQL file to include "proxy_protocol" field

It makes better the compliance with HSTS, http to https redirect must be done before domain to www.domain.

Implements #5290 in stable branch: Nginx - Allow certbot acme challenge on auth_basic protected websites

Add description text for logging options.

Fixed: #4307 The new LE ssl cert paths introduced in ISPConfig 3.1.1 where not set in the nginx_vhost.conf.master

The cipher suites are only set now for ISPConfig's own vhost, the intermediate security profile from Mozilla is used here.