build(gui-client/linux): include an empty firezone-tunnel binary with the Tauri deb package (#4220)

I thought this was going to use `cargo-deb` but it was actually easy
with the Tauri deb bundling we already use.

```[tasklist]
### Before merging
- [x] Make sure every file in the Tauri deb is also in our deb (e.g. icons)
```

scripts/build/tauri-rename-ubuntu.sh

@@ -23,3 +23,13 @@ function make_hash() {
 make_hash "$BINARY_DEST_PATH"-amd64
 make_hash "$BINARY_DEST_PATH"-amd64.dwp
 make_hash "$BINARY_DEST_PATH"_amd64.deb
+
+# TODO: There must be a better place to put this
+# Test the deb package, since this script is the easiest place to get a release build
+sudo dpkg --install "$BINARY_DEST_PATH"_amd64.deb
+
+# Debug-print the files. The icons and both binaries should be in here
+dpkg --listfiles firezone
+which firezone firezone-tunnel
+firezone-tunnel
+firezone || true

scripts/build/tauri-rename-windows.sh

@@ -6,10 +6,9 @@ ls ../target/release ../target/release/bundle/msi
 
 # Used for release artifact
 # In release mode the name comes from tauri.conf.json
-# Using a glob for the source, there will only be one exe, msi, and pdb anyway
-cp ../target/release/*.exe "$BINARY_DEST_PATH-x64.exe"
+cp ../target/release/Firezone.exe "$BINARY_DEST_PATH-x64.exe"
 cp ../target/release/bundle/msi/*.msi "$BINARY_DEST_PATH-x64.msi"
-cp ../target/release/*.pdb "$BINARY_DEST_PATH-x64.pdb"
+cp ../target/release/firezone_gui_client.pdb "$BINARY_DEST_PATH-x64.pdb"
 
 function make_hash() {
     sha256sum "$1"> "$1.sha256sum.txt"

scripts/tests/smoke-test-gui-windows.sh

@@ -32,13 +32,13 @@ function smoke_test() {
     done
 
     # Run the smoke test normally
-    cargo run -p "$PACKAGE" -- smoke-test
+    cargo run --bin "$PACKAGE" -- smoke-test
 
     # Note the device ID
     DEVICE_ID_1=$(cat "$DEVICE_ID_PATH")
 
     # Run the test again and make sure the device ID is not changed
-    cargo run -p "$PACKAGE" -- smoke-test
+    cargo run --bin "$PACKAGE" -- smoke-test
     DEVICE_ID_2=$(cat "$DEVICE_ID_PATH")
 
     if [ "$DEVICE_ID_1" != "$DEVICE_ID_2" ]
@@ -66,7 +66,7 @@ function crash_test() {
     rm -f "$DUMP_PATH"
 
     # Fail if it returns success, this is supposed to crash
-    cargo run -p "$PACKAGE" -- --crash && exit 1
+    cargo run --bin "$PACKAGE" -- --crash && exit 1
 
     # Fail if the crash file wasn't written
     stat "$DUMP_PATH"