Block ID is unstable when writing content in raw HTML

Nobody has claimed this yet.

### Search first

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

### What Happened?

> This is migrated from [#12323](https://github.com/logseq/logseq/issues/12323). It can be reproduced in logseq-og-1.0.0

I found that for blocks written in raw HTML, their block ID changes every time when reading the graph. for example the following two-page graph:

1. "page 1.md"
```markdown
- markdown
- id:: 6962f273-6224-4018-8bef-0331aa4d0e36
| A | B | C |
|---|---|---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
| 7 | 8 | 9 |
- html
-
id:: 6962f467-6626-4f9b-8830-31728a8d75be


A
B
C




1
2
3


4
5
6


7
8
9



-
```

Please note that I did not write `id:: XXXX` manully. They are generated by logseq.

2. "page 2.md"
```markdown
- markdown
- ((6962f273-6224-4018-8bef-0331aa4d0e36))
- html
- ((6962f467-6626-4f9b-8830-31728a8d75be))
-
```

In `page 2`, I referenced to the blocks in `page 1` and it works fine.

However, when I migerate the whole graph (folder) to another machine, the reference to HTML block breaks.

Returning to `page 1`, I found the block ID is re-generated and is different from the previous one.

On the original machine, the block ID is valid, so the reference is valid.

But if I click "Re-index" on the original machine, the block ID is also changed:

Causing the block reference breaks:

### Reproduce the Bug

1. write a block with HTML
2. reference that block
3. re-index the graph or migrate it to another machine
4. get broken block reference

### Expected Behavior

I expect block reference is stable no matter what I do with the graph (excluding modifing the reference itself)

### Screenshots

_No response_

### Desktop or Mobile Platform Information

Windows 11, Desktop OG app 1.0.0

### 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 by tracing how raw HTML blocks are parsed and assigned IDs during graph re-indexing, then compare that path with ordinary Markdown blocks. Reproduce the issue using the two-page graph and the listed re-index or migration steps; done means the HTML block ID remains unchanged and its reference continues to resolve.

Written by the indexing model from the issue text.