transaction_ignore_client_addresses

## Is your feature request related to a problem?
Nessus is a web vulnerability scanner. As part of its scan it makes a lot of unique HTTP requests, using a variety of User-Agents (including none at all).

## Describe the solution you'd like
Ability to exclude transactions originating from my known Nessus IPs.

## Describe alternatives you've considered
Trying to exclude them based on User-Agent (`transaction_ignore_user_agents`), but this can't cover them all, and may also exclude some regular traffic.

Blocking/deleting them downstream, but this still results in a lot of unnecessary overhead from the agent, including exceeding cardinality limits when `use_path_as_transaction_name` is enabled.

## Additional context
Addresses should be specifiable as ipv4, ipv6, and CIDR.

Start by locating the existing transaction_ignore_user_agents configuration and the transaction filtering or creation entry point. Determine where client IPs are available and how configuration values are parsed. Done means Nessus IPv4, IPv6, and CIDR addresses can be configured without excluding other traffic, with coverage for the supported address forms.

Scritto dal modello di indicizzazione a partire dal testo della issue.