build: fix platform compatibility

[jjl9807]

fix #75

[Copilot]

Pull request overview

This PR fixes platform compatibility issues by adding Buck2 compatible_with constraints to platform-specific Rust dependencies and removes an unused dependency. The changes prevent build failures when attempting to build on incompatible platforms.

• Added macOS-only constraint to system-configuration crate
• Added Windows-only constraint to hyper-named-pipe crate
• Removed unused internal-russh-forked-ssh-key dependency
• Updated buckal.snap fingerprint reflecting workspace changes

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
third-party/rust/crates/system-configuration/0.6.1/BUCK	Added compatible_with = ["prelude//os:macos"] to constrain build to macOS platform
third-party/rust/crates/hyper-named-pipe/0.1.0/BUCK	Added compatible_with = ["prelude//os:windows"] to constrain build to Windows platform
third-party/rust/crates/internal-russh-forked-ssh-key/0.6.11+upstream-0.6.7/BUCK	Deleted entire BUCK file for unused dependency
buckal.snap	Updated workspace fingerprint hash reflecting the dependency changes

Comments suppressed due to low confidence (1)

third-party/rust/crates/internal-russh-forked-ssh-key/0.6.11+upstream-0.6.7/BUCK:1

• This BUCK target previously compiled the internal_russh_forked_ssh_key crate with weak cryptographic options such as the rsa-sha1 feature and hazmat-allow-insecure-rsa-keys, which can enable SHA-1 based RSA signatures and insecure RSA key sizes in SSH key handling. An attacker who can influence which algorithms are negotiated or which keys are accepted could exploit these weaker primitives to degrade security compared to modern RSA+SHA2 with sufficiently large keys. Removing this target from the Buck build mitigates the issue here; if this crate is still built elsewhere, ensure it is configured to use only strong algorithms (e.g., RSA with SHA-256/512 and keys ≥2048 bits).