fix(NcAppNavigationItem): Fix popper boundary element

[ChristophWurst]

☑️ Resolves

• For Misplaced actions menues nextcloud/mail#8474

The query selector in the computed prop ran too early, before the element existed. There is no reactivity. Now the boundary element is set very late at mount, when the boundary element does exist in the DOM.

There are a few edge cases, but the menu positions better than before when the boundary fell back to the body.

🖼️ Screenshots

🏚️ Before	🏡 After
B	A

🚧 Tasks

• ...

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable
• 3️⃣ Backport to next requested with a Vue 3 upgrade

[GretaD]

I end up in the same scenario as you. I can reproduce the issue on main, then i link and the issue is gone. I do npm ci, kill the link and same as you i cannot reproduce it anymore.

[ChristophWurst]

Let's do this. It sets the element more reliably. I don't see a downside.

[susnux]

Makes sense because on mounted the parent should exist which is the content.

And the computed was wrong in the first place, it was never recalculated because document is not reactive

[susnux]

/backport to next