Add consent-scoped reliability and growth telemetry

[lihongguang-0014]

Scope

• Python source installs now attach the full validated Git commit to reliability app_version as base_version+source.<40-char-sha>; Gateway, CLI, and TUI use the shared sink.
• Unpackaged Electron source/development runs use the same identity. Official packaged Desktop releases keep ordinary semver because they have no checkout metadata.
• The dashboard already normalizes the encoded value, groups by release and source commit, and exposes the full sourceCommitId in the API while the UI shows a short display form.
• Growth events, updater semver comparison, endpoints, and the database schema remain unchanged.

Target

• main

Issue

• None

Release note

• None; this is a backward-compatible reliability-dimension enhancement.

Tests

• Python telemetry and dashboard suites: 615 passed, 2 skipped.
• Ruff and targeted mypy: passed.
• Electron build-identity and reliability telemetry tests: passed.
• Electron TypeScript build: passed.
• git diff --check: passed.
• Desktop Electron unit-test CI job: passed; remaining CI jobs are still running.

Safety and compatibility

• No prompt, response, file, account, or other user-content identifiers were added, and no new endpoints were introduced.
• Existing release-version rows remain readable; source rows are split only when a valid commit is present.
• Updater old_version/new_version and semver checks continue to use the plain application version.
• The deployed dashboard files were not changed in this follow-up, and no running telemetry service was restarted.

Third-party origin

• None; implementation and tests are repository-native.