feat: effect/schema form resolver

[tomsour1s]

I am currently working on a project where we heavily use the effect/schema library. To avoid adding another dependency for form validation, I have implemented a new resolver.

I believe this could be interesting and useful for others as well.
Would you consider accepting a merge request that adds this new resolver?

Here is a quick demo of how it works so far:

1. define a schema

const FORM_SCHEMA = Schema.Struct({
  id: Schema.String,
  startDate: Schema.DateFromSelf,
  endDate: Schema.DateFromSelf.pipe(
    Schema.annotations({ message: () => 'Please inter a valid Date or select a Date with the DatePicker' }),
  ),
  reason: Schema.String.pipe(
    Schema.minLength(4),
    Schema.annotations({ message: () => 'Has to be at least 4 chars long' }),
  ),
})

2. use the custom resolver with full support of the ParseOptions Object from effect/schema

const resolver = ref(effectSchemaResolver(FORM_SCHEMA, { errors: 'all' }))

3. example of the error message

[borsTiHD]

I find this new resolver implementation both interesting and highly useful. I would love to see this merge request considered for inclusion, as it simplifies validation logic and improves the developer experience for users of effect/schema without extra dependencies.

Looking forward to further feedback and hopeful for the integration of this resolver.