weave report duplicates ipam info, includes undocumented internals

[bboreham]

Example:

    "IPAM": {
        "Paxos": null,
        "Range": "10.32.0.0-10.47.255.255",
        "RangeNumIPs": 1048576,
        "DefaultSubnet": "10.32.0.0/12",
        "Ring": {
            "Start": "10.32.0.0",
            "End": "10.48.0.0",
            "Peer": 280247203912194,
            "Entries": [
                {
                    "Token": "10.32.0.0",
                    "Peer": 280247203912194,
                    "Version": 5,
                    "Free": 262144
                },
                {
                    "Token": "10.36.0.1",
                    "Peer": 227154428381508,
                    "Version": 1,
                    "Free": 262142
                },
...
        "Entries": [
            {
                "Token": "10.32.0.0",
                "Peer": "fe:e2:23:09:da:02",
                "Version": 5
            },
            {
                "Token": "10.36.0.1",
                "Peer": "ce:98:83:03:49:44",
                "Version": 1
            },

Basically everything under Ring is duplicated elsewhere, with the exception of the Free count in each entry, and it may be hard to explain that this count is out of date for non-local nodes.

I propose the Ring section be removed from weave status.

[bboreham]

Sorry, this error is new with #1702 so I will just fix it there.