Layout Builder cannot be uninstalled while menu_link_content overrides exist and unable to find these overrides anywhere visually or in db

Is this issue different than 🐛 Layout Builder cannot be uninstalled while overrides exist; no easy way to revert all overrides Needs work ?

In my opinion, the issue is different because #2980299 is related to the UX components and the destructive action as you perform it. In this case, I cannot find a way to expose UX elements for the element within question (menu_link_content.layout_builder__layout) to work with it and purge data.

The simplest explanation would be that I'm simply overlooking where this could be but I have dug and dug without any success, which is why I came here and referenced the other issue because it is "kind of close but not quite" to this particular issue.

I keep asking myself: "If there was a page to manage menu displays, where would it be?" -- I have never seen such a thing. But maybe layout builder had one at one time way back when?

@jlancaster, this doesn't address the general issue or explain how it might have gotten there in the first place, but curious if https://www.drupal.org/project/menu_item_extras → might at least help expose the field for you (since that module makes menu items fieldable, so providing "manage display" and similar forms for menus).

This was is quite tough to debug and feels like it may be an issue with the particlar site.

Out of the box Core has no way of attaching Layout Builder to Menu items so I expect some custom work was done to support that. @maxstarkenburg suggests one way that this may have been done.

I think to progress this any further we would need steps to replicate from a fresh install of D11. I suspect that 🐛 Layout Builder cannot be uninstalled while overrides exist; no easy way to revert all overrides Needs work will mostly fix the issues that have surfaced on this particular site.

No further updates have been made on this issue since asking for steps in replicate in the last comment over 3 months ago, so I'm now marking this one as closed. Thanks!

If this one can be replicaated with just core or other people see this, feel free to reopen or open a follow up issue. Thanks!