Hmm, this update still needs to be upstreamed. The maintainers are not so much concerned with this issue. I suppose that the majority of the LAVA users only use it to make simpler tests and does not require the level of attention of transparent logs like us.
You would need to patch it manually as a hotfix and reinstall at least the `lava_dispatcher/shell.py` script.
I can delegate this burden to the Mesa CI job submitter script if you think this procedure is not worth it. Still, it will make the submitter hackier as it already is and prone to eventual new fancy logs that use another sequence of special characters.

Related LAVA upstream issue: https://git.lavasoftware.org/lava/lava/-/issues/561