fix: bug-report endpoint /api collision (DEV-2114) + BugReportButton hydration (DEV-2017)

[pascal-klesse]

Fixes two bugs that affected built/deployed consumer apps. Releases are automated via semantic-release, so the package version is intentionally not hand-bumped — the merge of these fix: commits will trigger the appropriate patch release.

Fix 1 — DEV-2114: bug-report endpoint 404 on built/deployed apps

Root cause. The module registered its server handler at /api/bug-report and the useBugReport composable did $fetch('/api/bug-report'). Consuming Nuxt apps very commonly proxy all /api/** requests to a separate backend via Nitro routeRules. That catch-all swallows /api/bug-report, forwards it to the backend (→ 404), and bug.lt's own handler never runs. Reproduced live: a built app with an /api/** proxy returned 404 for POST /api/bug-report.

Fix. Move the endpoint off /api/ and make it configurable:

• New module option endpoint (string), default /_bug-lt/report (Nuxt-internal _-prefix style, like @nuxt/icon's /_nuxt_icon), which won't be caught by /api/** proxies.
• Exposed to the client via runtimeConfig.public.bugLt.endpoint = options.endpoint.
• Server: addServerHandler({ route: options.endpoint, ... }) (was hardcoded /api/bug-report).
• Client (useBugReport): const endpoint = useRuntimeConfig().public.bugLt?.endpoint || '/_bug-lt/report' (was hardcoded /api/bug-report) — server and client now always agree.
• Types updated in src/runtime.d.ts (PublicRuntimeConfig.bugLt.endpoint) and BugReportConfig.
• README documents the new endpoint option and why (consumers proxying /api/**).

The server handler file (bug-report.post.ts) is unchanged — the route is declared explicitly in addServerHandler, so only the registered route + client URL needed to change to match.

Fix 2 — DEV-2017: BugReportButton hydration mismatch + "Failed to resolve component: RouterLink"

Root cause. BugReportButton.vue rendered a floating Nuxt UI UButton inside <Teleport to="body"> during SSR. UButton resolves to ULink → NuxtLink with to=undefined, which renders an <a> on SSR but mismatches on client hydration → every page logged [Vue warn]: Failed to resolve component: RouterLink, Hydration node mismatch, and Hydration completed but contains mismatches.

Fix. The floating button is a pure client-side UI overlay, so its <Teleport>/<UButton> block is now wrapped in <ClientOnly> — it never SSR-renders, eliminating the mismatch. Position/color/screenshot/openModal behavior is unchanged. The modal (BugReportModal) needed no change: it is only ever mounted client-side via useOverlay().create() from a click handler (and the auto-mounted button is mounted via a separate createApp() in a client-only app:mounted hook), so it is never part of the SSR tree.

Build / lint / test

• npm run prepack (build via @nuxt/module-builder): succeeds.
• npm run lint (eslint): clean, 0 errors / 0 warnings.
• npm test (vitest): 8 files, 51/51 tests pass. Updated test/module.test.ts to assert the new default endpoint option and the addServerHandler route /_bug-lt/report (instead of the old /api/bug-report).

🤖 Generated with Claude Code

[pascal-klesse]

🎉 This PR is included in version 1.6.7 🎉