fix(node): Upload sparse files as regular entries

[yuanzui-cf]

Summary

Projects containing sparse files fail before dependency installation because Docker rejects GNU sparse tar entries with unhandled tar header type 83. Disable sparse encoding in the shared workspace/application upload helper so Docker receives regular file entries with the complete logical contents.

Preserve symlink handling. Add regression coverage for both build and SSR archive roots, sparse and ordinary file contents, and symlinks pointing outside the source directory. Sparse files now occupy their logical size in upload archives.

Validation

• cargo test -p grass-node runtime::socket::tests — passed (4 tests).
• just quality — passed (formatting, lint, Rust/Console tests and checks, builds, license checks).
• Verified the failing repository contains a sparse image file on the deployment host. Runtime image deployment and real-project retry follow the release workflow.

Tracking

Closes #193

Related deployment: #192; parent: #191.