[Cherry-pick #43136] [MVE 1.5.1] [Push AV] Increase blind duration an…

[raveendra-karu]

Summary

Cherry-pick of #43136

When the developer / tester verifying the TCs manually, the time taken to trigger motion events is not enough for the blind duration defined in the TCs. Due to this, sometimes, PAVST 2_13 fails as there is no expected response received from DUT.

Related issues

Fixes #42926

Testing

# Linux PC
#Console 1
./scripts/examples/gn_build_example.sh examples/camera-app/linux out/debug/
sudo rm -rf /tmp/chip_*; ./out/debug/chip-camera-app --app-pipe /tmp/pavst_2_13_fifo --camera-test-audiosrc --camera-test-videosrc

#Console 2
# Build python controller and active environment
scripts/build_python.sh -m platform -i out/python_env
source out/python_env/bin/activate

# Run Push AV TC
Example:
python3 src/python_testing/TC_PAVST_2_13.py --commissioning-method on-network --discriminator 3840 --passcode 20202021 --storage-path admin_storage.json --endpoint 1   --string-arg host_ip:localhost --app-pipe /tmp/pavst_2_13_fifo

# Press Enter whenever there is a motion command request comes on the terminal and immediately run console #3 command

#Console 3
echo '{"Name": "ZoneTriggered", "ZoneId": 1}' > /tmp/pavst_2_13_fifo

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for d74174b.

🟢 All jobs passed!

But CI Insights is watching 👀

[gemini-code-assist]

Code Review

This pull request increases the blind duration and transport expiry time for Push AV streaming tests. The changes are straightforward, primarily updating timeout constants. I've identified a minor opportunity to improve comments in one of the test files for better clarity and to correct a typo, in line with the repository's style guide.