Don't include historic transit stops

[nvkelso]

Looks like there's another use case around historic transit features we need to guard against.

• What did you see? A kind:stop feature in NYC for a stop that isn't in service, it's marked historic=yes at OSM.org.
• What did you expect to see? This feature shouldn't be included in tiles at all. It hasn't had service in a long time. We should only be showing current transit in our tiles.
• What map location are you having problems with? node 3039734895 in NYC at 5th Av and 3rd St.
• Screenshot?

/cc @bcamper

[nvkelso]

Moving to next release for load balancing.

[okavvada]

• Does this refer to transit stops only or all transit features?
• railway: stop is included in both the transit.yaml and the pois.yaml. Do we want to not include both layers if historic?
• Is it limited to historic=yes? or any historic tag value? example from TagInfo:
  historic = yes, historic = railway, historic = railway_station