fix(utils): default value for defaults as objects

[foyarash]

Reasons for making this change

fixes #4635

This PR fixes a situation where having a default set as an object, typically used for selects or radio buttons, would make the associated field frozen, with its value being impossible to change in the form.

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

[heath-freenome]

@foyarash Thanks for the fix AND it seems you and another person are making changes to the exact same code. Can you look at the other person's fix and see if how your changes may affect their PR?

[foyarash]

@heath-freenome hello, so I tested the PR with my changes. It seems to work but requires to add some extra condition on my side, so I guess I'll wait for the PR to be merged first

[Lonli-Lokli]

@foyarash I think @heath-freenome wants to merge yours first, actually :)
Can you try to add a few tests with array defaults, so I will be sure that my rebased PR will not break your code?

[foyarash]

@foyarash I think @heath-freenome wants to merge yours first, actually :) Can you try to add a few tests with array defaults, so I will be sure that my rebased PR will not break your code?

Actually i think it should be fine for the arrays, my PR doesnt have any impact on form datas that are arrays.