fix: stub globally registered components by alias

[ifer47]

Summary

• resolve component registration names from the app-level component registry when matching global.stubs
• keep local component registration names as the first priority, then fall back to global registrations and existing script setup/name inference
• add a regression test for components registered by a plugin under a public alias that differs from the component's internal name

Root Cause

getComponentRegisteredName() only inspected the parent component's local components option. Components installed through plugins or libraries with app.component('GlobalAlias', Component) were resolved by Vue at runtime, but Vue Test Utils could only see the component's internal name. As a result, global.stubs.GlobalAlias did not match unless the internal component name happened to be the same.

Fixes #2541.

Validation

• pnpm test tests/mountingOptions/global.stubs.spec.ts -t "globally registered component by its registration name" --run
• pnpm test tests/mountingOptions/global.stubs.spec.ts --run
• pnpm test tests/mountingOptions/global.components.spec.ts --run
• pnpm test --run
• pnpm run lint
• pnpm run vue-tsc
• pnpm exec oxfmt --check src/utils/componentName.ts tests/mountingOptions/global.stubs.spec.ts

[netlify]

✅ Deploy Preview for vue-test-utils-docs ready!

Name	Link
🔨 Latest commit	4a27c45
🔍 Latest deploy log	https://app.netlify.com/projects/vue-test-utils-docs/deploys/6a428837cd724300081d2dc3
😎 Deploy Preview	https://deploy-preview-2895--vue-test-utils-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.