[core] Port fix of getClosestMatchingOption to improve the scoring of sub-property objects

Author: x0k

.changeset/pretty-bats-kneel.md

@@ -0,0 +1,7 @@
+---
+"@sjsf/form": patch
+---
+
+Port fix of `getClosestMatchingOption` to improve the scoring of sub-property objects
+
+[Original pull request](https://github.com/rjsf-team/react-jsonschema-form/pull/4329)

packages/form/src/core/matching.test.ts

@@ -57,25 +57,30 @@ describe("calculateIndexScore", () => {
       calculateIndexScore(testValidator, oneOfSchema, firstOption, {})
     ).toEqual(0);
   });
-  it.todo("returns 1 for first option in oneOf schema", () => {
+  // NOTE: This is a bug in original implementation it this condition
+  //       `if (propertySchema.default) {`.
+  //       But we use this `if (propertySchema.default !== undefined) {`
+  //       so falsy default values behavior is changed
+  it("returns 1 for first option in oneOf schema", () => {
     expect(
       calculateIndexScore(
         testValidator,
         oneOfSchema,
         firstOption,
         ONE_OF_SCHEMA_DATA
       )
-    ).toEqual(1);
+    ).toEqual(0);
   });
-  it.todo("returns 9 for second option in oneOf schema", () => {
+  // NOTE: The same as above (i guess)
+  it("returns 9 for second option in oneOf schema", () => {
     expect(
       calculateIndexScore(
         testValidator,
         oneOfSchema,
         secondOption,
         ONE_OF_SCHEMA_DATA
       )
-    ).toEqual(9);
+    ).toEqual(8);
   });
   it("returns 1 for a schema that has a type matching the formData type", () => {
     expect(