Enable client_ip (ACL) support for Handles

[Monviech]

Example Usecase:

• You have a handle and you want to limit access to certain IP ranges, for example private IP ranges. If your OPNsense Firewall only has one public IP address, this can't be configured by using firewall rules.

• An ACL will get a named handler, with an UUID, just as subdomains do now.

• The ACLs will get their own menu in the GUI.

• Each ACL will be a tokenized field where a number of IPv4 or IPv6 addresses or cidr ranges can be input.

• Each ACL will get an additional checkbox to invert the match if needed.

Then if enabled, they will create something like this:

Example configurations for exact domains:

example.com {
        @29978007-445d-4bcc-a894-23241asd1cfc {
                client_ip 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8 127.0.0.1/8
        }
        handle @29978007-445d-4bcc-a894-23241asd1cfc {
                handle {
                        reverse_proxy 172.16.0.173 {
                        }
                }
        }
}

Example configuration for subdomains with TLS:

*.example.com {
        @cdd470d0-525d-4c93-b2a8-5fa4f476942f {
                host foo.example.com
        }
        handle @cdd470d0-525d-4c93-b2a8-5fa4f476942f {
                @29978007-445d-4bcc-a894-23241asd1cfc {
                        client_ip 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8 127.0.0.1/8
                }
                handle @29978007-445d-4bcc-a894-23241asd1cfc {
                        handle {
                                reverse_proxy 172.16.0.173 {
                                        transport http {
                                                tls
                                        }
                                }
                        }
                }
        }
}

Example with not matcher:

example.com {
        @29978007-445d-4bcc-a894-23241asd1cfc {
                not client_ip 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8 127.0.0.1/8
        }
        handle @29978007-445d-4bcc-a894-23241asd1cfc {
                handle {
                        reverse_proxy 172.16.0.173 {
                        }
                }
        }
}