Invalid completion for `metaobject` type schema settings

Describe the bug
On adding a metaobject schema setting in a section, for example, the default key is suggested.

On trying to upload a setting with this key, the CLI reports that default is not a valid attribute

Source

// sections/test.liquid

{% schema %}
{
  "name": "Test",
  "settings": [
    {
      "type": "metaobject",
      "id": "test",
      "label": "Test",
      "metaobject_type": "test",
      "default": "test"
    }
  ]
}
{% endschema %}

Expected behaviour
default is not suggested as a key for metaobject schema settings

Actual behaviour
default is suggested as a key for metaobject schema settings

Debugging information

• OS: masOs
• OS Version: Sequoia 15.3.1

Reproduce the schema completion and CLI validation using the provided sections/test.liquid example. Trace the metaobject schema-setting completion and validation entry points, then verify that default is no longer suggested while valid attributes remain available.