refactor: consolidate CLI binaries and streamline CI workflows

[senamakel]

Summary

• Consolidated Rust CLI binaries by removing legacy openhuman-cli/openhuman-core bins and introducing a unified openhuman binary.
• Updated runtime and service wiring (core_process, core_server, service module exports) to align with the new binary layout.
• Cleaned up CI workflows by removing deprecated pipelines and tightening remaining workflow configs.
• Moved frontend HTML entrypoint to src/index.html and adjusted Vite/Tailwind/polyfill references accordingly.
• Reduced dependency footprint and lockfile noise by removing unused packages and related config surface.

Problem

• The repository had overlapping/legacy CLI binaries and stale workflow files, which increased maintenance overhead and made release/build behavior harder to reason about.
• Frontend build/config paths had drifted, creating avoidable complexity during local and CI builds.

Solution

• Replaced multiple Rust binary entrypoints with a single maintained openhuman binary and updated affected runtime integration points.
• Removed obsolete GitHub Actions workflows and updated active workflow files to match the current release/build process.
• Standardized frontend entrypoint/config references after moving index.html under src/.
• Pruned unused dependencies and synchronized configuration updates in package.json, vite.config.ts, and lockfile.

Testing

• yarn -s compile
• cargo check --manifest-path src-tauri/Cargo.toml
• Other checks run (list commands)
• Ran via pre-push hook during git push:
  • prettier --check .
  • eslint . --ext .ts,.tsx
  • tsc --noEmit
• Manual validation completed (list scenarios)

Impact

• Primarily impacts desktop/CI/release tooling and Rust CLI/runtime packaging paths.
• No intended end-user feature behavior changes; main effect is reduced maintenance complexity and cleaner build/release pipeline surface.

Breaking Changes

• None
• Yes (describe clearly, including migration steps)

Related

• Issue(s): N/A
• Follow-up PR(s)/TODOs:
  • Consider a focused CI follow-up to validate removed workflows are no longer referenced by release automation/docs.