Handle serialization edge cases

[pianostardom]

Describe the bug and the expected behavior

Since the defaultValue object gets serialized automagically down the call stack in useForm, there exists an edge case for utility functions such as getInputProps (e.g. with types checkbox/radio) to which a user may pass a non-serialized value inadvertently.

The problem here is that e.g. the defaultChecked field will be falsy due to type mismatch (e.g. number/string, etc).

PS. For future reference to those who search issues but not discussions, here's a short overview of how serialization works: #433

Conform version

v1.2.2

Steps to Reproduce the Bug or Issue

Maybe another time?

What browsers are you seeing the problem on?

Chrome, Firefox, Microsoft Edge, Safari, Others

Screenshots or Videos

No response

Additional context

No response