fix(ci): do not keep logging if grep times out or finds the string

[gustavovalverde]

Motivation

Even though we tried to fix this in #7713, it was still not working on that PR.

Solution

• Use >(...) which is a form of process substitution in Bash, which avoids the "broken pipe" error as the tee command isn't directly writing to a closed pipe

Review

If added a 5 min timeout here, so if this passes it should be good to go.

Reviewer Checklist

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info? (new features, breaking changes, large changes)
• Are the PR labels correct?
• Does the code do what the ticket and PR says?
  • Does it change concurrent code, unsafe code, or consensus rules?
• How do you know it works? Does it have tests?

[gustavovalverde]

I changed this back to Draft as it's still not working.

I'll be testing a new approach locally and in CI using other Docker options for logging

• https://docs.docker.com/engine/reference/commandline/logs/#options
• https://docs.docker.com/config/containers/logging/configure/#supported-logging-drivers

[teor2345]

If we install ripgrep on our Google Cloud machine, we could use rg --passthru ... rather than tee ... | grep ....

rg accepts the same arguments as grep.

[mpguerra]

@gustavovalverde do we still need this one?