fix(#2591): findComponent doesn't not return exposed properties in vm

[adamberecz]

After investigating the issue down to @vue/runtime-core it appears that exposeProxy is only set in a script-setup component if it uses at least one directive:
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/component.ts#L1187
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/directives.ts#L143

Meaning a component can have an exposed API while exposeProxy is null. In this case we can create manually from exposed which essentially has the same effect, because the one created by runtime-core is only different by also proxying publicPropertiesMap which aren't available anyway.

[netlify]

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

Name	Link
🔨 Latest commit	eb826a7
🔍 Latest deploy log	https://app.netlify.com/projects/vue-test-utils-docs/deploys/68dbd3a202f4430007139177
😎 Deploy Preview	https://deploy-preview-2715--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.

[cexbrayat]

Thank you for looking into it. Would you mind adding a unit test that showcases that the issue no longer exists?

[cexbrayat]

Hi @adamberecz

Would you mind adding some unit tests to the PR so we can merge it?

[adamberecz]

I've stumbled upon another issue related to using devtoolsRawSetupState which might not be available in some cases. I'm still investigating it as it might also affect this behavior. I'll get to you and possibly update the PR (+ add some tests).