fix(types): align error object types with JS object structure

[Thomaash]

🔎 Overview

This PR aligns types of errors object destructured from useForm with the JS object that is actually returned (the issue is described in more detail in #4295).

🤓 Code snippets/examples (if applicable)

Before:

type Step = {
  name: string
}

type Form = {
  steps: Step[]
}

type Result = Path<Form> // `steps` | `steps.${number}` | `steps.${number}.name`, fails at runtime

Now:

type Step = {
  name: string
}

type Form = {
  steps: Step[]
}

type Result = Path<Form> // `steps` | `steps[${number}]` | `steps[${number}].name`, works at runtime

✔ Issues affected

closes #4295

[changeset-bot]

🦋 Changeset detected

Latest commit: 53e1de3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
vee-validate	Patch
@vee-validate/joi	Patch
@vee-validate/nuxt	Patch
@vee-validate/rules	Patch
@vee-validate/valibot	Patch
@vee-validate/yup	Patch
@vee-validate/zod	Patch
@vee-validate/i18n	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[logaretm]

Many thanks for tackling this, LGTM. I worry it may cause breaking changes, but since the errors object currently is typed incorrectly, I think this is fine to have.