[dschmidt]

Description

buildUrl(router, to) now accepts everything router.resolve accepts, not only a path string. String calls behave as before.

// before
buildUrl(router, router.resolve({ name: 'pastebin-view', params }).fullPath)
// after
buildUrl(router, { name: 'pastebin-view', params })

I ran into this in the pastebin app (opencloud-eu/web-extensions#628), which needs an absolute link to its own route. With a route location, the route name stays the single source of truth and the extra lookup goes away.

Also in this PR:

• Query fix: in history mode the href was assigned to URL.pathname, so a query came out as /app/view%3Fx=1.
• Call sites: the picker modals, the editor links opened in a new tab and the pathchange event built URLs with window.location.origin by hand and now use buildUrl. With the default <base href="/"> nothing changes. In hash mode they dropped the current path, and the pathchange URLs missed the # and, under a sub path, the base path.
• Test setup: production builds always have <base href="/">, unit tests had none, so vitest.init.ts now adds it.

Related Issue

• [pastebin] Link copied after creation opens folder view instead of pastebin content web-extensions#628

How Has This Been Tested?

• new buildUrl unit tests with a real router: named routes with params and query, hash and history mode, with and without base path; the query cases fail without the fix
• full unit test suite, eslint, prettier, vue-tsc

Types of changes

• Bugfix
• Enhancement (a change that doesn't break existing code or deployments)
• Breaking change (a modification that affects current functionality)
• Technical debt (addressing code that needs refactoring or improvements)
• Tests (adding or improving tests)
• Documentation (updates or additions to documentation)
• Maintenance (like dependency updates or tooling adjustments)