OG versions (0.10.15 & 1.0.0) incorrectly show updates to DB 2.0.1

Nobody has claimed this yet.

### Search first

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

### What Happened?

As of today, both my long‑running Logseq OG 0.10.15 installation and a fresh install of Logseq OG 1.0.0 are prompting me to update to Logseq 2.0.1. My understanding is that OG users must avoid updating to DB as they are now separate versions for markdown and DB.

### Reproduce the Bug

1) Via Homebrew, observe Homebrew wanting to upadte Logseq version 0.10.15 to version 2.01.

2) Within the app:
Settings>General>Check for update
Observe the update prompt for version 2.0.1.

### Expected Behavior

Logseq OG should only show update notifications for OG‑track releases, not DB releases.

### Screenshots

_No response_

### Desktop or Mobile Platform Information

macos
Logseq OG versions tested: 0.10.15, 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 the update-check flow reached through Settings > General > Check for update and compare it with the Homebrew update path for OG 0.10.15 and 1.0.0. Confirm that both paths offer only OG-track releases and never DB 2.0.1, then exercise the listed versions on macOS.

Written by the indexing model from the issue text.