Default value from subschema used for string autocompletion elsewhere

Describe the bug

The default value of a property in one subschema is unintentionally used as default value in string item property.

I have a json schema like so:

{
  "$defs": {
    "Foo": {
      "properties": {
        "foo": {
          "type": "string",
          "default": "hello"
        }
      },
      "type": "object"
    }
  },
  "additionalProperties": false,
  "properties": {
    "foos": {
      "items": {
        "$ref": "#/$defs/Foo"
      },
      "type": "array"
    },
    "bars": {
      "items": {
        "type": "string"
      },
      "type": "array"
    }
  },
  "required": [
    "bars",
    "foos"
  ],
  "type": "object"
}

The completions for this schema is shown like this:

correctly showing the default value for foo but also showing ${1} for bar. When hitting enter, the default value is applied to the bar element as well:

Expected Behavior

I expect the default value to only show up for the property it is defined for.

Current Behavior

Default value shows up unexpectedly in wrong place.

Steps to Reproduce

1. Copy the schema
2. ctrl + space in new file which uses the schema
3. hit enter

Environment

• Windows
• Mac
• Linux
• other (please specify)

Reproduce the issue in VS Code using the provided schema: trigger completion in a new file and compare the foos and bars array items. Trace the completion path for JSON Schema defaults, then verify that hello is offered only for foo and is not inserted for bar.