fix(NcActions): handle expensive height computation by popover library

[Antreesy]

☑️ Resolves

• Replaces fix(NcActions): Use full window height #5806
  • autoBoundaryMaxSize lets floating vue resize the popper inner container to the available size
  • drawback - losing feature of showing 50% of last item cropped, if it doesn't fit the screen
  • benefits - no more jumping and second re-render (first by library, then manually by us), no memory leaks

🖼️ Screenshots

🏚️ Before

2025-11-05_11h22_00.mp4

🏡 After

2025-11-05_11h17_43.mp4

🚧 Tasks

• Check effect on Memory/Performance
• Check for side effects

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable
• 2️⃣ Backport to stable8 for maintained Vue 2 version or not applicable

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.75%. Comparing base (82d7687) to head (b95e84b).
⚠️ Report is 41 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7778      +/-   ##
==========================================
+ Coverage   51.41%   51.75%   +0.34%     
==========================================
  Files          96       96              
  Lines        3147     3126      -21     
  Branches      867      863       -4     
==========================================
  Hits         1618     1618              
+ Misses       1279     1262      -17     
+ Partials      250      246       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[susnux]

So while it now takes full height, it looses the main reason for the manual resizing:
If the content is longer than the boundary then we want to have it cut off at 50% of the element so the user knows about that there is more to scroll.
With only the library it does no longer cut off at 50% of the next element.

So codewise I am fine, but just needs approval of @jancborchardt (added that feature).

[Antreesy]

so the user knows about that there is more to scroll.

Drawback would be then only for browsers, who don't show the scrollbar by default, right?

[jancborchardt]

Really nice improvement so I’d approve. :) We can check later if there is adjustment needed for cutting of at 1/2 of entries, or if that’s an issue at all (probably depending on system and scrollbar visibility).

[susnux]

Isnt this solved by #7808 ?

[Antreesy]

Isnt this solved?

Performance - mostly solved.
But it still triggers re-rendering of a popover after mounting, it looks jumpy and frozen, if trigger button is scrolled (up and down). So I would still like to opt in for native library solution

[susnux]

code makes sense and so as design agrees this is fine :)

[ShGKme]

@Antreesy backport?

[Antreesy]

/backport to stable8