WIP Updates to the ambiguous_crossing_tags validator

(re: #1210)

- Handles all types of crossing conflicts and updates, tons of edge cases
- Includes all the entities way/node in a single issue
- Improved UI, code simplification, for the tag conflicts/upgrades
- prefer the shorter name 'ambiguous_crossing' over `ambiguous_crossing_tags`
- candidateCrossing check is still there, but commented out

css/80_app.css

@@ -3560,7 +3560,9 @@ li.issue-fix-item button:not(.actionable) .fix-icon {
 .issue-info.expanded {
     display: inline-block;
 }
-
+.issue-info .suggested-update {
+    margin-top: 10px;
+}
 .issue-info .issue-reference {
     margin-bottom: 10px;
 }
@@ -3584,6 +3586,11 @@ li.issue-fix-item button:not(.actionable) .fix-icon {
 .issue-info .tagDiff-cell-remove {
     background: #fdd;
 }
+.issue-info .tagDiff-message {
+    padding: 2px 10px;
+    font-family: monospace;
+    font-size: 10px;
+}
 
 
 /* Background - Display Options Sliders

data/core.yaml

@@ -1829,16 +1829,24 @@ en:
         message: "{feature} ends very close to itself but does not reconnect"
       highway-highway:
         reference: Intersecting highways should share a junction vertex.
-    ambiguous_crossing_tags:
+    ambiguous_crossing:
       title: Ambiguous Crossing Tags
-      message: "Line and point disagree about markings"
-      message_markings: "Line has marking '{marking1}' but point has marking '{marking2}'"
+      message:
+        conflict: Crossing line and point tags conflict
+        update: Crossing tags can be updated
       incomplete_message: "Point may be missing crossing information."
       incomplete_reference: "Point looks like it may be updated to a crossing."
       tip: "Crossing line markings conflict with crossing point"
       reference: Line and point must either be both marked or both unmarked.
       upgrade_node: "Upgrade point to:"
       upgrade_way: "Upgrade way to:"
+      not_a_crossing: "(not a crossing)"
+      annotation:
+        changed: Changed crossing tags
+      fix:
+        update_type: "Update tags for a '{type}' crossing"
+        choose_type: "Tag this crossing as '{type}'"
+        remove_all: Remove all crossing tags
     area_as_point:
       message: '{feature} should be an area, not a point'
     close_nodes: