Fix/reanimate patrol tests

[Kendru98]

Hi, Flutter Team, as Patrol team, we want to reanimate patrol tests that were disabled.

Important

This repository is a testing suite that contains references to tests (in the registry directory) that are run with every commit to Flutter
to verify that no breaking changes have been introduced (in the "customer_testing" shards). Your merged PR is not automatically run in the
Flutter CI tree.

After merging this PR, you must send another PR to flutter/flutter updating dev/customer_testing/tests.version in that repo with the latest git commit SHA of the flutter/test repo.

See flutter/flutter#162048 for details.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read the Flutter Style Guide recently, and have followed its advice.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Kendru98]

CLA signed ✅