oneOf not selecting correct option for objects with the same property keys but different default, read-only values

[zmagauina-fn]

Prerequisites

• I have read the documentation;
• In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.
• Ideally, I'm providing a sample JSFiddle or a shared playground link demonstrating the issue.

Description

A oneOf schema with two objects with the same property but different read-only, default values won't correctly select the option with the matching value for the key when passed a formData, and instead will match the first option with the correct property keys (both the property keys are the same).

Steps to Reproduce

In this playground example, you can see that the two oneOf options both have the same properties (one "lorem" key), with different read-only, default values.
2. If you select the second option, it will update formData to { "lorem": "second" }. If you select the first option, formData becomes { "lorem": "first" }. This is the expected behavior.
3. If you now change formData to { "lorem": "second" }, it will keep the selector on the first option, but change the name to "second".

Expected behavior

Per the example above, I'm trying to initialize the selector on the second option using the formData value.

I have data objects with the same keys but different default, read-only values that represent different options. I want to be able to initialize the selector at the correct option based on the formData passed in.

Actual behavior

The isValid check inside the getMatchingOption method in utils will return true when comparing the following schema:

{
    "properties": {
        "lorem": {
            "type": "string",
            "default": "first",
            "readOnly": true
        }
    },
    "required": [
        "lorem"
    ]
}

and formData:

{
  "lorem": "second"
}

Even though the it's a default, read-only value and the values don't match.

Version

"@rjsf/core": "^2.4.0"

[yair-dana]

I had the same problem.
after I used 'const' instead 'readonly' it works

const: 'second'