feat(core)!: change the implementation of validationMode

[Mini-ghost]

🔗 Linked issue

No issues linked to this PR

❓ 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 like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Currently, Vorms's validationMode and reValidationMode support blur, change, submit and input. All modes except input rely on the corresponding native event, while the input mode relies on the implementation of setFieldValue().

The current implementation caused two problems:

1. Unintuitive, you may not want to trigger validation when calling setFieldValue() manually.
2. Integration with some UI frameworks is error-prone.

This PR will resolve that, it is going to support input mode with native events.

📝 Checklist

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

[Rock070]

Minimal Reproduction - stackblitz

Context: Using validateMode: input with Vuetify.

Click reset button, Vuetify built in reset handler run after Vorm reset, so the form would be validated because the Vuetify reset handler trigger the setFieldValue.

This PR solved the problem to me.