Fix clippy::semicolon_if_nothing_returned warnings

[Copilot]

This PR fixes two clippy::semicolon_if_nothing_returned warnings to ensure consistent formatting across the codebase.

Changes

Added semicolons to statements that return nothing (unit type ()) in two locations:

1. crates/fspy_preload_unix/src/interceptions/spawn/exec/mod.rs - Added semicolon after pre_exec.run()? in the exec handler
2. crates/fspy/src/command.rs - Added semicolon after the self.envs assignment statement

Why

The clippy lint semicolon_if_nothing_returned encourages consistent formatting by requiring semicolons on statements that don't return a value. This makes the code more readable and follows Rust's style conventions.

Before:

pre_exec.run()?

After:

pre_exec.run()?;

Testing

• All existing tests pass (71 tests)
• Verified with cargo clippy --workspace -- -W clippy::semicolon_if_nothing_returned - no warnings remain

Original prompt

Fix clippy::semicolon_if_nothing_returned warnings

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR fixes two clippy::semicolon_if_nothing_returned warnings by adding semicolons to statements that return the unit type ().

Key Changes

• Added semicolons to two statements that don't return values to comply with Rust style conventions
• Ensures consistent formatting across the codebase

Reviewed Changes

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

File	Description
crates/fspy_preload_unix/src/interceptions/spawn/exec/mod.rs	Added semicolon after pre_exec.run()? call
crates/fspy/src/command.rs	Added semicolon after .collect() assignment

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}