chore(test): silence Vue warnings in the unit test suite

[eddieferrer]

What

Cuts [Vue warn] output from npm run unit from 75 to 3, with no change
to what the suite covers: 299 files / 4412 tests pass before and after, none
added, skipped, or removed.

The noise made it hard to spot a real failure in CI output, and two of the
warnings turned out to be masking actual spec bugs (see below).

Why the shared config is split two ways

test/unit/setup.js gets the defaults that can't collide — the kvTrackEvent
directive and an apollo provide, via VTU config.global. Specs' own global
blocks merge on top and still win.

test/unit/specUtils.js gets routerLinkStub and mockRouterObject as
opt-in helpers. These deliberately are not global: registering RouterLink
or providing vue-router's routerKey suite-wide collides with the three specs
that build a real router (BasketItem, ThanksPageSingleVersion,
RouteListing), where <router-link> is expected to render an anchor with
role="link". My first attempt did make them global and broke
BasketItem's getByRole('link').

routerLinkStub renders a literal <router-link to="..."> element, matching
the DOM Vue emitted while the component was unresolved. That's intentional:
specs query router-link[to="..."] (TeamMessageCard) and getAttribute('to')
(TeamCard). The goal is to silence the resolve warning, not to change rendered
output — so this PR changes no assertions.

Two spec bugs the warnings were hiding

• BadgeMilestone.spec.js spread globalOptions at the top level of its
  render options, where VTU ignores directives/provide/mocks entirely.
  Its mocks were inert across all 8 tests. Now global: globalOptions.

• useMyKivaHome.spec.js called the composable bare in 2 of 11 tests, so
  its onMounted had no instance to attach to. Both now wrap it in a
  TestComponent like the other nine.

  The reactive computed properties test asserts pre-fetch defaults, which
  depends on the mount hook not having completed. Its assertions stay
  synchronous after render(): onMounted fires, but its apollo query
  resolves on a later microtask, so the values are still the defaults. The flip
  to /mykiva after resolution is covered by two sibling tests, which confirms
  that assertion isn't trivially true.

Two import-order constraints, documented in the files

Both cost a debugging cycle, so they're comments where the next person will hit
them:

• setup.js must not import from #src. Importing KvAuth0 pulled in
  syncDate before syncDate.spec.js could vi.mock('timesync'), breaking all
  10 of its tests.
• specUtils.js must not import routerKey from vue-router. Several specs
  vi.mock('vue-router') without re-exporting it, and the import broke their
  collection. The one spec that needs the key imports it directly.

The 3 remaining warnings

All intentional or out of scope:

Warning	Status
injection "apollo" not found	Intentional — test named "should not query when apollo is not provided"; uses raw createApp, so config.global never applies
Invalid prop: custom validator "state"	Intentional — FeaturedGoalCard deliberately passes state="something-unsupported"
Invalid prop: type check "to"	Pre-existing bug in RouteListing.vue:56, tackled separately

Testing

• npm run unit — 299 files / 4412 tests pass, exit 0
• npm run lint — exit 0 (the 7 remaining warnings are pre-existing GraphQL
  schema warnings in untouched files)
• No product code changed; test/ only

[kiva-robot]

🎉 This PR is included in version 3.81.0-rc.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[kiva-robot]

🎉 This PR is included in version 3.81.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀