[Bug] Journal default template reverts to previous version and loses content after incremental update

Nobody has claimed this yet.

### Search first

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

### What Happened?

When I create a template (named verion1) for `#journal`, it work initially. After update the template incrementally (named version 2), it works some day and went back to version 1 one day unexpectedly.
Meanwhile, copy the new content in template into Journal will cause them disappear, as the screenshot display.

### Reproduce the Bug

1. Create a template (v1) and `Apply template to tags: Journal`
2. Generating some Journals transferring template (v1)
3. Update the template incrementally (v2), like changing the heading style, adding new block, changing icon
4. Generating some Journals transferring template (v2)
5. Journals may transferring back to template (v1) some day later
6. Copy blocks in template (v2) and paste in Journal, you may see the original v1 blocks disappear in template

### Expected Behavior

fix this bug

### Screenshots

### Desktop or Mobile Platform Information

windows 11, logseq DB v2.0.1

### Additional Context

In screenshot, the Journal has transferred back to template(v1)

### 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 numbered template-update and Journal-copy steps on Windows 11 with Logseq DB v2.0.1. Done means an incrementally updated template remains on version 2 after several days, and copying its blocks into a Journal does not make the original version 1 blocks disappear.

Written by the indexing model from the issue text.