`name` option in `logseq.Editor.upsertProperty` not working

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I wrote a plugin and create some properties via `logseq.Editor.upsertProperty` method:

```js
const properties = {
key: { schema: { type: 'default' }, opts: { name: "Jira Key" } },
url: { schema: { type: 'url' }, opts: { name: "Jira URL" } },
type: { schema: { type: 'default' }, opts: { name: "Jira Issue Type" } },
[...]
}

for (const [key, meta] of Object.entries(properties)) {
await logseq.Editor.upsertProperty(key, meta.schema, meta.opts)
}
```

The properties are created, but the name is ignored and the key is used as name.

The not working feature is described here: https://github.com/logseq/logseq/blob/master/libs/guides/db_properties_references.md#upsertpropertyname-schema-opts

### Reproduce the Bug

1. create a simple plugin
2. call: `await logseq.Editor.upsertProperty("my_test", { schema: { type: 'default' }, [meta.opts](opts: { name: "My Test" }))`
3. check created property

### Expected Behavior

Created property should use the name as display name.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

_No response_

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Start with the documented upsertProperty(name, schema, opts) reference and trace the logseq.Editor.upsertProperty implementation. Reproduce the call using opts.name, then verify that the created property uses the supplied value as its display name rather than the key.

Written by the indexing model from the issue text.