UX: unable to create property with same name as page (only suggest converting)

Nobody has claimed this yet.

### Search first

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

### What Happened?

tienson said [here](https://github.com/logseq/db-test/issues/350#issuecomment-3004163946):

> logseq db does allow sharing the same name between different types, such as tags, properties and pages.

so the UX should allow that

### Reproduce the Bug

1. Create page "ppp"
2. Click "Set property"
3. Type "ppp"

### Expected Behavior

Option to create new property with that name, in addition to converting the page. Not sure if that should be the default option.

### Screenshots

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

NixOS 26.05.4193.a50de1b7d8a5
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260710

### Additional Context

#### Workaround

Create new property "ppp3", then rename to "ppp".

### 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 by reproducing the issue through the “Set property” flow: create page “ppp”, then type “ppp”. Trace the UI entry point that handles the suggestions and property creation; done means the flow offers creating a property named “ppp” in addition to converting the page, with the behavior verified against the reported workaround.

Written by the indexing model from the issue text.