fix(test-scripts): pin cargo run --bin perry so multi-bin workspace doesn't break parity

The styling-matrix binary added in v0.5.300 (#185 Phase A) created a second
workspace binary alongside `perry`. Without `--bin perry`, `cargo run --quiet --`
errors with "could not determine which binary to run", which the parity
runner reports as "compile error" for every single test. All open PRs have
been red on parity since v0.5.300 hit origin/main.

Same fix applied to run_tests.sh.

Author: proggeramlug

run_parity_tests.sh

@@ -215,7 +215,7 @@ for test_file in "$TEST_DIR"/*.ts; do
     echo "$node_output" > "$node_output_file"
 
     # Compile with Perry
-    compile_output=$(cargo run --quiet -- $BACKEND_FLAG "$test_file" -o "$perry_binary" 2>&1)
+    compile_output=$(cargo run --quiet --bin perry -- $BACKEND_FLAG "$test_file" -o "$perry_binary" 2>&1)
     compile_exit=$?
 
     if [[ $compile_exit -ne 0 ]]; then

run_tests.sh

@@ -68,9 +68,9 @@ for test_file in "$TEST_DIR"/*.ts; do
     fi
 
     # Compile the test (suppress warnings)
-    if ! cargo run --quiet -- "$test_file" -o "$output_file" 2>/dev/null; then
+    if ! cargo run --quiet --bin perry -- "$test_file" -o "$output_file" 2>/dev/null; then
         # Try again to get error message
-        compile_output=$(cargo run --quiet -- "$test_file" -o "$output_file" 2>&1 | grep -i "error" | head -3)
+        compile_output=$(cargo run --quiet --bin perry -- "$test_file" -o "$output_file" 2>&1 | grep -i "error" | head -3)
         echo -e "${RED}FAIL${NC}  $test_name (compile error)"
         if [[ -n "$compile_output" ]]; then
             echo "       $compile_output"