Feat: Allow raising errors from within a custom whatever(#2718)

[abdalla-rko]

Reasons for making this change

I introduced a raiseFieldErrors method to raise errors from within a custom component(see #2718).

The current behavior allows errors to be raised from custom components and when the form onChange is triggered, we clear the custom raised errors. I appreciate any feedback on this approach. If everything looks good, I'll write tests and implement this in other themes.

Checklist

• [ ] I'm updating documentation
  • [ ] I've checked the rendering of the Markdown text I've added
• [ ] I'm adding or updating code
  • [ ] I've added and/or updated tests. I've run npm run test:update to update snapshots, if needed.
  • [ ] I've updated docs if needed
  • [ ] I've updated the changelog with a description of the PR
• [ ] I'm adding a new feature
  • [ ] I've updated the playground with an example use of the feature

[heath-freenome]

@abdalla-rko If the goal is to update the errorSchema via a custom widget, maybe it makes sense to update the onChange in WidgetProps to function similarly to the onChange in FieldProps, where the errorSchema can be updated as it is flows through the schema hierarchy. Feel free to join the next meeting so we can talk about it. Or reach out to me on Discord