["floating" feature branch] Add useKFloatingPosition

[MisRob]

Description

The first PR in the series that aims to prepare selected parts of #1114 for production environment. Targets floating-production feature branch. The next PR will be for useKFloatingInteraction.

Adds useKFloatingPosition composable with new documentation pages

• Browser support
• Floating elements
• useKFloatingPosition

Note that Floating UI may be replaced by Popper, depending on results of browser testing in Kolibri & dev discussion (the structure of the composable and documentation will be the same for both, except few differences).

Issue addressed

Part of #1158

Changelog

Skipped. Will prepare the changelog before merging the feature branch to develop.

AI usage

I used Claude for draft and then further assistance when iterating on it. There's not a place that I wouldn't tweak or see ;) Also self-reviewed the final diff fully.

[rtibblesbot]

Clean, focused addition of useKFloatingPosition with solid documentation.

CI passing. Verified the three new/updated docs pages (useKFloatingPosition, floatingelements, browsersupport) and the interactive tooltip example against the Netlify preview — all render correctly, the DocsWarning component is visually consistent, and the tooltip example works as expected. No design spec to compare against; color-contrast and html-lang a11y violations are pre-existing site-wide issues.

• suggestion: missing .catch() on the computePosition promise — see inline
• suggestion: test mock resolves with {} but no assertion covers the style update — see inline
• nitpick: partial mock leaves middleware exports undefined — see inline
• praise: defensive cleanup before re-init, verified by tests — see inline

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Reviewed the pull request diff checking for:

• Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
• Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
• Architecture: duplicated concerns, minimal interfaces, composition over inheritance
• Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
• Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
• Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
• Checked CI status and linked issue acceptance criteria
• For UI changes: inspected screenshots for layout, visual completeness, and consistency

[rtibbles]

All changes make sense to me.