Per the parent task, we'd like to start introducing AbuseFilter protected variables that use data from iPoid-Service.

In this task, we will implement a variable tentatively named ip_reputation_tunnel_operators. This variable corresponds to the tunnels.operator property in spur.us data.

Acceptance criteria:

• A protected variable called ip_reputation_tunnel_operators can be added to an AbuseFilter filter
• Saving an AbuseFilter filter with ip_reputation_tunnel_operators will only be possible if the filter is protected, and the filter and its logs are visible only to users with the right to edit/view fiiters with protected variables
• on edit, the filter will perform an API request to iPoid-Service with the client IP, and obtain the tunnels.operator property as a string. AbuseFilter filters should be able to match against the array of operators.