Can't disabled well-known (letsencrypt) path protection

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
I have a service which lives behind NPM, it needs to be able to request its own SSL certificate as its used for other purposes than simply web access. It's a commercial product I can't change. By default NPM seems to include './etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf' which returns a 404 for a request to the /well-known/ URL space, as a protection system. However, this prevents the underlying system from using letsencrypt to make the request.

I tried to use the advanced section to change this location, however nginx emits a warning about duplicate locations and doesn't work.

I don't see any way to stop this default behaviour or get around it using NPM.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

1. setup a small nginx server with the URL path on port 80
2. add the proxy host to NPM
3. try and request the file (URL)

Expected behavior
A checkbox to turn off letsencrypt protection for that proxy host (stops the inclusion of this file)

Operating System

Additional context

Start with etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf and trace how it is included for a proxy host, then inspect the proxy-host advanced settings flow. Reproduce the duplicate-location warning with a small backend and verify that a per-host option can disable the protection without breaking other proxy hosts.