Form validation properties

[itpropro]

Description

For custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties touched and dirty exposed.

• Touched (opposite of untouched): A field is considered touched when a user has focused it OR changed it's value
• Dirty (opposite of pristine): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.

You can currently work around most of these by using a computed on the exposed errors ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.

Additional context

No response