Layout additional paths are displayed as overrides even if they're not, in some cases

[herbdool]

This is a follow-up to #1528. Given a view that has two pages with unique routes:

A layout that overrides those routes, will state that even routes not included in that view are overrides (like for -3, -4, -5):

I noticed it's only doing it for paths ending in numbers so suggests a faulty regex.

[herbdool]

Looks like it's merely determining this with _layout_menu_router_path_exists() which pre-exists the recent merged PR. And it looks in the menu_router table for rows that match the path. So seems like it's more about why menu_router has entries for those paths.

[herbdool]

Or maybe it is this PR which should have been more discriminating. _layout_menu_router_path_exists() returns results even if the additional path for the same layout is in the menu_router table. So it'll only display this after saving and re-editing. At that point the path appears with the layout_page_callback in the table. The function should probably parse the results and check that the page arguments do not match the layout being edited.

[herbdool]

I've got a PR for this. It actually fixes a pre-existing problem for the main path too, but is more visible now that someone can add multiple paths. Now if it's path created by the layout it won't show "overridden" because it's not. In this example the main path and the second path are both Views pages as well, but the third is unique to this view.

[quicksketch]

Thanks @herbdool, I took a quick look at the PR. I'll need to have fresh mind/eyes to really understand it, so I'm going to put this into the 1.31.1 milestone.