fix(stubs): teleport stub children as a function

[cexbrayat]

Fixes#1829

I'm not super convinced by this fix, but it indeed looks like @freakzlike intuition is right: we need to return the children as a function for Teleport to avoid the warning.

Maybe @xanf you have a better idea on how to handle that?

[netlify]

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

Name	Link
🔨 Latest commit	60268e6
🔍 Latest deploy log	https://app.netlify.com/sites/vue-test-utils-docs/deploys/635a870bdabf1f0008818af0
😎 Deploy Preview	https://deploy-preview-1833--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.

[freakzlike]

I have no better solution for this.
Can you add a spy on console.warn on one of the teleport tests?

[cexbrayat]

@freakzlike I added a test to check that the warning is not logged anymore, and added a check in other tests when it is logged, but when that we expect it.

Maybe we should do the same for the warnings logged by vue compact (either mock them or fix them if needed) to avoid polluting the test logs, and missing a regression like this one in the future

Anyway, this should fix the issue, unless someone comes up with a better idea. I'll let you give a last check and merge

[lmiller1990]

This does feel like a bit of a hack, but okay for now. I am not sure of a better way.

Warnings are not much fun. let's merge this up with one more ✅ and release.