High Level Overview

Provide a first pass at adding inhighway tag based osm data to the options of encoded data.
The Goal: To provide traffic signal, stop signs, and traffic crossings back in the routing requests.
The Outcome: The routing API's can provide details on traffic signals, stop signs, and crossing along your route

More Details

The encoded data (tags) being targeted are references in the highway-tag wiki page:highway-tag under the "Other highway features".
Currently, the tags that are being included are

• traffic_signals
• stop
• crossing
• links provided to osm wiki pages

Additionally, this provides a channel to add on additional tags under thehighway key using this encoded_data tag.

graph.encoded_values: highway_feature

This also provides the ability to request those highway features (currently traffic signals, stop signs, and crossing) from the web api via thedetails parameter

I attempted to model this after other encoded_value tags and parsers, but am very happy to refactor or adjust as needed. If this data is better loaded using other methods, I am glad to refactor as well. Open to any critiques as this is my first contribution here. Thanks for the time!

Note:

• added username and blurb to CONTRIBUTORS.md file
• tests created and themvn clean test verify passing locally (and on the new test)
• made an attempt to update the example config, but glad to provide more documentation on this in a different area if there is an apatite.