test: change compliance test rerun condition regex string

[Linchin]

This PR tries to reproduce the system test failure recorded in #969.

This PR fixes a group of compliance tests failures opened by flaky bot: #938 ~ #1002

After investigations it seems the rerun conditions of the compliance test, which work as regex match, did not catch the intended errors as the error messages' format has changed. Updated the strings so the compliance tests pass.

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

[chalmerlowe]

@Linchin
Two things (not sure if you already know this or not):

if we are gonna change the noxfile.py for this testing, there may be some cases where the owlbot processor may run and revert all our changes to the noxfile.

To avoid this while we test the noxfile.py changes we can apply the owlbot:ignore label.

When it comes time to make changes to owlbot.py to create any needed updates in the noxfile.py, we have a local owlbot docker container that can simplify the testing to make sure owlbot.py is successful in creating all the edits we need.

[Linchin]

@chalmerlowe

Thank you for the reminder about owlbot! I definitely forgot about it, but lucked out as owlbot somehow did not run. I'll make sure owlbot.py is modified correctly in the final PR. I'll message you individually about the details to run the owlbot container.

[parthea]

but lucked out as owlbot somehow did not run

I believe this is WAI. Owl bot won’t run automatically when PRs are created from a fork (for security reasons).

[chalmerlowe]

LGTM