ignore SLOW SQL Query in OCR2 chaos tests

[Tofel]

Fixes: https://github.com/smartcontractkit/chainlink/actions/runs/24815937830/job/72631888292#step:12:129

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

Failed Test	Failure Summary	Logs
TestSample	The test failed because a condition that should be false was true.	Logs ↗︎
TestIntegration_Functions_MultipleV1Requests_ThresholdDecryptionSuccess	The test failed without a specific error message, but the logs indicate an issue occurred during the integration test execution.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[Copilot]

Pull request overview

Risk Rating: LOW — test-only change that adjusts log-scanning expectations during cleanup.

This PR updates the OCR2 chaos test cleanup log scanning to treat “SLOW SQL QUERY” log lines as expected during chaos (container disruption), preventing the test run from failing due to this known/benign message.

Changes:

• Add zapcore import to support specifying an allowed log message severity.
• Extend products.DefaultSettings(...) in TestOCR2Chaos cleanup to allow/ignore "SLOW SQL QUERY" during log scanning.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube