orion: deploy client to GCE VM via SSH

- add workflow_dispatch trigger so forks can run the workflow manually
- build orion and scorpio in CI and upload artifacts
- deploy binaries to a GCE VM over SSH using ORION_DEPLOY_HOST/ORION_DEPLOY_SSH_KEY
- replace previous gcloud-based scp/ssh steps with plain ssh/scp

Signed-off-by: Hongze Gao <15101764808@163.com>

Author: WiedersehenM

.github/workflows/orion-client-deploy.yml

@@ -16,7 +16,6 @@ concurrency:
 
 jobs:
   build:
-    # 允许 upstream 正常触发，同时在 fork 中可以通过 workflow_dispatch 手动触发
     if: ${{ github.repository == 'web3infra-foundation/mega' || github.event_name == 'workflow_dispatch' }}
     runs-on: ubuntu-latest
     timeout-minutes: 20
@@ -56,7 +55,6 @@ jobs:
             target/release/scorpio
 
   deploy:
-    # upstream 继续限制只在主仓库触发；在 fork 中可以通过 workflow_dispatch 手动触发
     if: ${{ github.repository == 'web3infra-foundation/mega' || github.event_name == 'workflow_dispatch' }}
     runs-on: ubuntu-latest
     needs: build
@@ -65,14 +63,9 @@ jobs:
       fail-fast: false
       matrix:
         include:
-          # 单台 VM 示例：使用仓库 Secrets ORION_DEPLOY_HOST_1 / ORION_DEPLOY_SSH_KEY_1
           - name: orion-vm-1
             host_secret: ORION_DEPLOY_HOST_1
             ssh_key_secret: ORION_DEPLOY_SSH_KEY_1
-          # 如需多台，再追加：
-          # - name: orion-vm-2
-          #   host_secret: ORION_DEPLOY_HOST_2
-          #   ssh_key_secret: ORION_DEPLOY_SSH_KEY_2
 
     env:
       ORION_DEPLOY_HOST: ${{ secrets[matrix.host_secret] }}