Allow disabling default failure predicates.

[mergeconflict]

Works on #826

[mum4k]

Looks like the CI failed, because README needs to be regenerated.

Could you try running this locally and uploading the commit?

tools/update_cli_readme_documentation.sh --mode fix

Additionally we should add both a unit test and an e2e test for the new feature. The unit test should live here and the integration test probably here.

[mergeconflict]

Could you try running this locally and uploading the commit?

tools/update_cli_readme_documentation.sh --mode fix

Done, thanks!

Additionally we should add both a unit test and an e2e test for the new feature. The unit test should live here and the integration test probably here.

I've added a unit test. I agree an e2e test would make sense, but I'm having some trouble constructing one, maybe you have some advice... My issue is that I can't find a way to configure NH test server to send error responses, which is necessary to verify that there aren't any failure predicates. Any suggestion?

[mum4k]

Without looking closer - could we achieve the same by pointing Nighthawk to a port the test server isn't listening on?

[mum4k]

Looks great, glad this approach worked out. I have two minor requests aiming to make the integration test case more understandable.

[mum4k]

Looks good, thank you for moving the code to the utility library.

Looks like the CI is failing due to formatting of Python files, could you execute ci/do_ci.sh fix_format and see if that helps?

[mum4k]

Thank you @mergeconflict !