chore(release): bump VERSION to 0.10.8 for next cycle

[LukasWodka]

Summary

Declares 0.10.8 as the next release version so the release train can cut an rc for it.

v0.10.7 is already tagged and shipped to prod, and the delta waiting on develop
(#505, feat(ingest): guided mode always asks, pre-filled) touches internal/cli/* —
a declared publish_path in release-train's repos.yml. With VERSION still reading
0.10.7, the staging hop's version preflight refuses:

rc NOT tagged - v0.10.7 already exists and the delta DOES touch published files
(bump VERSION on develop before the next release)

Patch-level, matching every release in this series (0.10.1 → 0.10.7 were all patch
bumps, features included).

Type

chore(release)

Test plan

No behavior change — VERSION is read by release.yml at tag time and by the train's
version preflight. CI on this PR covers the build; the train's settle stage is what
proves the guard is satisfied.

Checklist

• Targets develop
• Single self-contained change
• No secrets or customer data

---

Note

Low Risk
Single-file version bump with no application logic or security impact.

Overview
Bumps the declared release version in VERSION from 0.10.7 to 0.10.8 for the next release cycle.

This is a bookkeeping-only change so release-train version preflight and tag-time reads in release.yml see a new version while v0.10.7 is already tagged and develop has further deltas (e.g. ingest guided-mode work under internal/cli/*). No runtime or CLI behavior changes.

^{Reviewed by Cursor Bugbot for commit 5e8668c. Bugbot is set up for automated code reviews on this repo. Configure here.}