Please add the ability to assign multiple access lists to proxy hosts.

Is your feature request related to a problem? Please describe.

Currently, a Proxy Host can be assigned only one Access List. This is limiting when different access rules need to be applied simultaneously.

For example, I may need to allow access for users from one IP range while also requiring authentication for another group of users. With only one Access List per Proxy Host, these access policies cannot be combined easily.

Describe the solution you'd like

Please add the ability to assign multiple Access Lists to a Proxy Host.

Ideally, the Proxy Host configuration should allow selecting multiple Access Lists, with the option to define how they are evaluated (for example, allowing access if a request matches any of the selected lists).

This would make it possible to combine different access policies without creating duplicate Proxy Hosts or manually modifying the Nginx configuration.

Describe alternatives you've considered

The current workaround is to create separate Proxy Hosts or manually modify the generated Nginx configuration, but these approaches are inconvenient and can be overwritten when Nginx Proxy Manager regenerates its configuration.

Another option is to create one large Access List containing all required rules, but this is not practical when the same access lists need to be reused independently across multiple Proxy Hosts.

Additional context

It would be especially useful to be able to reuse existing Access Lists and combine them on a per-Proxy-Host basis.

For example:

Proxy Host: example.com
Access List 1: Internal networks
Access List 2: VPN users
Access List 3: Administrators

This would provide much more flexibility for managing access to Proxy Hosts.

Start by tracing how Proxy Host configuration and Access Lists are represented in the frontend and backend, then follow how the generated Nginx configuration applies a selected Access List. Define and test the evaluation behavior for multiple lists, including whether access is allowed when any selected list matches, and verify that reusable lists work without manual configuration changes.