feat(Form): add standard schema support to UI v2

[Gerbuuun]

🔗 Linked issue

resolves #2879

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Adds standard schema support to forms in UI v2

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[OhB00]

Any idea why this is different in v3?

The current version breaks Valibot schemas, this would fix that, but I can't tell if Valibot is wrong, the current implementation is wrong, or this PR is wrong?

[Gerbuuun]

I don't remember why I changed it when I copied it from v3.

Since the beta versions, valibot only supports the standard schema spec.
Valibot changed its implementation several times. That's why Nuxt UI v2 uses 3(!!) different Valibot versions...
This is to prevent breaking changes.

Nuxt UI is not wrong. Valibot is not wrong. This PR might be wrong lol. (it works for me though)
But yeah, I hope @romhml can take a look soon?

For now you can patch Nuxt UI with the changes in this PR