From T357772: Investigate: How will `ip_in_range` and `ip_in_ranges` function when temporary accounts are enabled, create a user_ip variable to expose the IP to AbuseFilter filters. IPs can't be store in the variable dump, as blobs are append only and the IP needs to be cleared from the database after 90 days. Instead, user_ip:

• will be lazy loaded and is the IP of temporary accounts or anonymous users
  • In practice, this IP should only be revealed for temporary accounts but by also exposing it for anonymous users, the migration path for filters will be simpler (swap user_name for user_ip instead of having to maintain both)
• on saving to the variable dump for storage, transform user_ip into a boolean value
• on loading the variable dump, transform user_ip (if true) back into an IP, grabbing it from afl_ip, a column in abuse_filter_logs that gets cleared on a schedule via maintenance script

This variable will need to be protected/restricted; see follow-up tasks for a breakdown of that work.