[DB Version 2.0.1] Cyrillic tags written as plain text without auto-complete break into #[[uuid]] format upon re-entering the block

Nobody has claimed this yet.

In the new DB version, writing a Russian/Cyrillic tag via # as plain text (without choosing it from the auto-complete dropdown menu) breaks the block rendering.

## Steps to Reproduce
- Open a clean block in Journals
- Write any text, then add a Cyrillic tag manually (e.g., #исследование) **without using auto-complete/suggestions**
- Move focus to another block (the tag might render on the right side)
- Click back inside the edited block

## Actual Behavior
The tag changes its format to #[[uuid]] inside the text instead of remaining a right-aligned badge. It only remains on the right side if explicitly selected from the auto-complete popup.

## Expected Behavior
Manually typed tags without auto-complete should be indexed correctly as DB tags and should not collapse into internal UUID brackets.

## Environment
Logseq Version: 2.0.1
OS: Windows 11

https://github.com/user-attachments/assets/2ac1e884-d8bb-4857-a41e-d9eef3c10278

Start by reproducing the issue in a clean Journals block using a manually typed Cyrillic tag, then move focus away and back to confirm the #[[uuid]] transformation. Trace the tag parsing and block-rendering paths involved in re-entering the block; done means manually typed tags remain indexed as right-aligned DB tags without internal UUID text.

Written by the indexing model from the issue text.