deprecation rule: specify list of possible "replace" resolutions

[tyrasd]

sometimes tags are deprecated, but don't have a 1:1 correspondence to a single new tag, but instead a (small) set of possible new tagging variants could be used as a replacement. currently, this is not possible to model using the deprecated.json schema. Something like this would be more powerful:

  {
    "old": {"oldkey": "oldvalue"},
    "replace": [
        {"description": "option A", "tags":  {"newkey": "newvalue1"}},
        {"description": "option B", "tags":  {"newkey": "newvalue2"}}
    ]
  },

iD could then show the two (or more) options in the tag upgrade widget alongside the given (translated) descriptions.

[tyrasd]

other examples:

• https://wiki.openstreetmap.org/wiki/Tag:sport=hockey
• https://wiki.openstreetmap.org/wiki/Tag:sport=skating
• https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dwell
• https://wiki.openstreetmap.org/wiki/Tag:shop=winery