OCSP Stapling switch

[BatSmacker84]

With this PR Dead, Proxy, and Redirect Hosts are now able to have OCSP Stapling enabled via the webgui with a simple toggle in the SSL tab.

The two config options added when OCSP Stapling is enabled are:

ssl_stapling on;
ssl_stapling_verify on;

The file used for OCSP Stapling is already provided by certbot (chain.pem), so all this PR does is allow for that stapling to occur by enabling those two options in each site's .conf file.
This is already possible in the current version of NPM by putting the two options into the Advanced Settings, but this PR allows for the config to look nicer and makes it easier for users to implement across their proxies.

The database does have to be migrated (a new migration file is included) in order to store if the Host has OCSP Stapling enabled or not.

[nginxproxymanagerci]

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-3151

Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

[TheNytangel]

Suggested change

	ssl_stapling on;
	ssl_stapling_verify on;
	ssl_stapling on;
	ssl_stapling_verify on;
	{% if certificate.provider == "letsencrypt" %}
	ssl_trusted_certificate /etc/letsencrypt/live/npm-{{ certificate_id }}/chain.pem;
	{% else %}
	ssl_trusted_certificate /data/custom_ssl/npm-{{ certificate_id }}/fullchain.pem;
	{% endif %}

Should ssl_trusted_certificate be included as well?

From the nginx docs:

For verification to work, the certificate of the server certificate issuer, the root certificate, and all intermediate certificates should be configured as trusted using the ssl_trusted_certificate directive.

Please note that, in my suggestion, I'm unsure about the custom SSL chain 🙂

[github-actions]

PR is now considered stale. If you want to keep it open, please comment 👍