refactor(hierarchy): name no screen for a tree Transitional calls a cross-fade

ScreenName kept its own reading of the route markers and disagreed with
Transitional on a marker repeated by a nested node: it named the screen on
a step the runner was skipping as unsettled. One reading now.

internal/hierarchy/hierarchy_test.go

@@ -1840,15 +1840,6 @@ func TestScreenNameNamesTheRouteTheTreeShows(t *testing.T) {
 			]}`,
 			"HomeScreen",
 		},
-		{
-			"route marker repeated by a nested node",
-			`{"attributes": {"bounds": "[0,0,10,10]"}, "children": [
-				{"attributes": {"resource-id": "HomeScreen", "bounds": "[0,0,10,10]"}, "children": [
-					{"attributes": {"resource-id": "HomeScreen", "bounds": "[0,0,10,5]"}, "children": []}
-				]}
-			]}`,
-			"HomeScreen",
-		},
 		{
 			"cross-fade names no screen",
 			`{"attributes": {"bounds": "[0,0,10,10]"}, "children": [