Add Appalachian Trail club operators

[quincylvania]

This is a draft PR to help illustrate and open up discussion around #10865. The data format would need to be better defined, but this is a start. The data is for the 30 member clubs that maintain the Appalachian Trail (relation/156553), all mapped in OSM and linked to Wikidata.

[bhousel]

This might be ok if we can get consensus what features these operators would go on, and if operator really is the right tag for what these organizations do.

Do you see it as like:

A big route relation with

name = Appalachian Trail
type = route
route = ?
network = nhn?
wikidata = Q620648
operator = Appalachian Trail Conservancy
operator:wikidata = Q2858589

And that route holds a bunch of member routes like (the things in this PR):

name = ?
type = route
route = ?
network = rhn?
wikidata = ?
operator = New York-New Jersey Trail Conference
operator:type = private
operator:short = NYNJTC
operator:wikidata = Q17083031

And then those member routes hold the different highway=whatever members?

There some pieces of this that NSI wouldn't be able to match without code changes (the superroute and the individual segments), and some pieces that it might be able to support today (the regional routes? idk).

I'm not sure that the operator is the thing that defines these features, so I'm handwaving a bit.

(edit: I think national highways are set up this way too, probably inconsistently)