Fix parameter write response validation

[gemenerik]

Parameter writes were incorrectly treating echoed values as error codes, causing all successful parameter sets to fail with 'Error setting the parameter: code X' where X was the actual value being set.

Root cause: The firmware echoes back the successfully written parameter value, but the Rust implementation was checking byte 2 for an error code (expecting 0 for success).

Fix: Compare the echoed bytes with the expected parameter value bytes to verify the parameter was set correctly.

Tested: Resolves parameter setting failures in (upcoming) example where stabilizer.estimator could not be set to value 2. Can be tested by modifying test_params.rs

[Copilot]

Pull Request Overview

Fixes parameter write response validation by correctly interpreting firmware echoed values instead of treating them as error codes. The firmware echoes back the successfully written parameter value, but the previous implementation was incorrectly checking for error codes, causing all successful parameter sets to fail.

• Changed validation logic to compare echoed bytes with expected parameter value bytes
• Updated error message to provide more detailed information about validation failures
• Fixed successful parameter writes that were previously failing with false error codes

---

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