Packaging through WhiteBeam installer produces incorrect hash file

[noproto]

The resulting .SHA256 file produced by cargo run package contains a relative path to the WhiteBeam package, which will produce an error when run through sha256sum -c (or equivalent command).

Erroneous output:

$ cat WhiteBeam_0.2.6_aarch64.SHA256
e192e16265df05403a7aaa544234f74bf7f1957ada5ac7042b06ff1bbe78ddb6  ./target/release/WhiteBeam_0.2.6_aarch64.tar.gz

Expected output:

$ cat WhiteBeam_0.2.6_aarch64.SHA256
e192e16265df05403a7aaa544234f74bf7f1957ada5ac7042b06ff1bbe78ddb6  WhiteBeam_0.2.6_aarch64.tar.gz

Needed for reproducible builds.

[noproto]

Relevant lines:

WhiteBeam/src/installer/platforms/linux/mod.rs

Lines 171 to 172 in 93d956c

	"sha256sum ",
	"./target/release/{}.tar.gz > ./target/release/{}.SHA256;"), package_name, package_name, package_name);