fix: formData change clear errorMessage

[JinYuSha0]

Reasons for making this change

fixes #4426

If this is related to existing tickets, include links to them as well. Use the syntax fixes #[issue number] (ex: fixes #123).

If your PR is non-trivial and you'd like to schedule a synchronous review, please add it to the weekly meeting agenda: https://docs.google.com/document/d/12PjTvv21k6LIky6bNQVnsplMLLnmEuypTLQF8a-8Wss/edit

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 npx nx run-many --target=build --exclude=@rjsf/docs && 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

[JinYuSha0]

formData change should behave the same as onChange method, I have implemented this

[heath-freenome]

@JinYuSha0 Please update the CHANGELOG.md to add a new 5.24.0 section since you are adding a new feature to @rjsf/utils. And make the few suggested changes. Also, provide 100% unit tests for the getChangedFields() function.

Also, these unit test, when written, should help you fix the test failures that exist in your PR.

[heath-freenome]

For better Typescript compatibility, unknown is preferred over any

Suggested change

	export default function getChangedFields(a: any, b: any): string[] {
	export default function getChangedFields(a: unknown, b: unknown): string[] {

[heath-freenome]

Suggested change

	* @param {any} a - The first object, representing the original data to compare.
	* @param {any} b - The second object, representing the updated data to compare.
	* @param a - The first object, representing the original data to compare.
	* @param b - The second object, representing the updated data to compare.

[JinYuSha0]

I think I'm done with this

[heath-freenome]

@JinYuSha0 I just merged another fix to the method you are changing... Can you first check to see if that fix also fixes the issue you are attempting to fix with this PR? Thanks. If not, then rebase that change into your PR first.

[JinYuSha0]

@heath-freenome

I pulled the latest commit in the main branch and executed build, it seems that this problem has not been solved, thank you very much for your attention to this issue.

git log --oneline
f5a24b25 (HEAD -> main, origin/main, origin/HEAD) Bug: schema with conditions where switching to then/else subschemas did not reflect the actual validation errors in the onChange event. (#4432)
c2a60d44 Bug: Issue with formData not updating when dependencies change (#4388)

[heath-freenome]

@JinYuSha0 In that case, would you be willing to rebase your changes on the latest and deal with the conflicts so that we can get your fix in?

[heath-freenome]

Also, it looks like your changes are breaking a core test. Can you investigate and fix?

[JinYuSha0]

I fix the breaking core test

1. change formData then error should be disappears.
2. when formData is srting, deepEquals again