fix: return the correct name when stubbing a script setup component

[hershelh]

When stubbing a component using the <script setup> syntax test-utils can't return its name correctly, so it skips the stub and the stub fails.There's an issue that describes the problem.
This is because getComponentName() function doesn't return its __name property.

[netlify]

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

Name	Link
🔨 Latest commit	14bb306
🔍 Latest deploy log	https://app.netlify.com/sites/vue-test-utils-docs/deploys/63306bc87924ab0008ba60b2
😎 Deploy Preview	https://deploy-preview-1783--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 site settings.

[cexbrayat]

Thanks @joeyhuang0235

Can you add a test that checks this change please?

[hershelh]

OK, I'll do it later

[hershelh]

@cexbrayat If I want the test case to run expectedly I have to install unplugin-vue-components and add it to Vitest configiration file like this:

It only works on the AutoImportScriptSetup component I specify and does not affect other components. Is it OK?

[cexbrayat]

I guess we can, if that solves a specific issue for this plugin.

Is it possible to limit the application of this plugin only to the test you are adding?

[hershelh]

I think I can't. As long as a component is imported, the plugin will take effect, so I can't limit the scope of this plugin to a test, but only control the target it transforms. So I specified that it can only transform the AutoImportScriptSetup component

[cexbrayat]

Ok, it should be good enough. Push your test and we'll take a look 👍

[cexbrayat]

Just a few nits, and we're good to merge 👍

[cexbrayat]

You need to run pnpm i again to update the lockfile, and we should be ready to merge

[hershelh]

Ok, sorry I forgot

[cexbrayat]

Awesome, thanks @joeyhuang0235