add tor_instances fact

[jcgl17]

This set_fact call gives other roles access to the ipv4+orport combination that is used to key various things, such as service instances and the various CSV files used by relayor. That makes it easier for other roles to compose neatly with relayor.

[jcgl17]

Made this a little more useful. Now the output looks something like this:

{
  "relay1.example.com-192.0.2.1_9002": {
    "instance_id_unqualified": "192.0.2.1_9002",
    "ipv4": "192.0.2.1",
    "ipv6": "2001:db8::1",
    "port": { "dirport": 0, "orport": 9002 }
  },
  "relay1.example.com-192.0.2.1_9004": {
    "instance_id_unqualified": "192.0.2.1_9004",
    "ipv4": "192.0.2.1",
    "ipv6": "2001:db8::1",
    "port": { "dirport": 0, "orport": 9004 }
  }
}

The top-level JSON keys are what is needed to select from relayor's various CSV files (e.g. to get an instance's nickname). instance_id_unqualified is a string that I've seen used in systemd service names on Linux (e.g. tor@192.0.2.1_9004.service).

This commit is backwards-incompatible with the last one, but now it has a flexible schema which shouldn't have to make further backwards-incompatible changes.

[jcgl17]

Rebased cleanly against v25.0.0.

[jcgl17]

Rebased cleanly against v26.0.0.

[nusenu]

To support d3619b3 we have a new fact that has all the important fields now: - IPv4 - IPv6 - ORPort - DirPort Other vars like inventory_hostname are available anyway. Since it can be used to construct all the fields you appear to include as well does that meet your requirements already?