More input to edge costs and LTS

- [ ] Fully separated cycletracks next to a motorway aren't great. Maybe just project perpendicularly (or buffer and look for overlaps) and check the speed / classification of the parallel road. https://www.openstreetmap.org/way/153773332
- [ ] Separated paths through greenspace can sometimes be nice, but may be uncomfortable at night. https://www.openstreetmap.org/way/933851270
- [ ] Similarly, industrial land use as the surrounding thing may feel uncomfortable. https://www.openstreetmap.org/way/166148979

For all of these, I think we could first just detect this situation about the edge (and surface that info in the UI clearly). Then we can write edge cost and LTS functions that take these things into account, using TBD weightings.

And a further idea: local knowledge (or routing preference) is always going to be helpful. If we have a way in the UI to just annotate a road and edit the LTS / edge cost manually, then that could be super helpful.