feat(ci): add PR-safe snap package validation

Problem Statement

snap-package.yml is only called from the release workflows and combines snap build/pack with Snap Store upload. As a result, PRs that change snap packaging, snapcraft input layout, or workflow copy paths do not validate the snap pack path before merge.

Recent release failures showed this gap:

• #1855 fixed an invalid actions/download-artifact pin, but the failure was only caught on the main release workflow.
• #1859 fixed a stale wrapper path after the release workflow progressed further and failed while preparing snap/prebuilt/.

Proposed Design

Split PR-safe snap validation from release publishing:

• Add a PR-safe workflow or job that builds/packs the snap without Snap Store credentials, deployment environments, or snapcraft upload.
• Reuse the same binary artifact layout and snap/prebuilt/ assembly path as the release workflow where practical.
• Consider factoring shared snap input assembly into a script or reusable action so PR and release validation exercise the same logic.
• Start with amd64-only PR validation to control runtime and runner cost. Keep the full amd64/arm64 matrix for release workflows.
• Keep release workflows responsible for publishing to latest/edge and latest/stable using SNAPCRAFT_STORE_CREDENTIALS.

A cheap static packaging asset check may also be useful. For example, validate that workflow copy sources exist and that the files required by snapcraft.yaml are produced by the snap assembly step.

Alternatives Considered

• Keep validating only in release workflows. This misses packaging regressions until after merge.
• Add snap-package.yml directly to pull_request. This is not appropriate as-is because the workflow currently requires release credentials/environments and always uploads to the Snap Store.
• Add only static checks. This catches stale paths, but does not prove snapcraft pack still works.

Agent Investigation

• snap-package.yml currently has only on: workflow_call.
• It is called from release-dev.yml and release-tag.yml.
• It requires publish-credentials, mapped to SNAPCRAFT_STORE_CREDENTIALS.
• It always runs snapcraft upload --release ....
• It depends on release workflow artifacts named cli-linux-*, gateway-binary-linux-*, and supervisor-binary-linux-*.
• Run 27299497855 showed #1855 fixed action resolution, then the snap job failed later during Prepare snap build directory due to the stale deploy/snap/bin/openshell-gateway-wrapper path.

Start by reading snap-package.yml, release-dev.yml, and release-tag.yml, then inspect the artifact names and the Prepare snap build directory step. Trace how snap/prebuilt/ is assembled and where SNAPCRAFT_STORE_CREDENTIALS and snapcraft upload are used. Done means PRs can run amd64-only snap packing without credentials or publishing while release workflows retain their existing matrix and upload behavior.