Split apart large integration tests logs files on Github Actions

[snario]

In the optimism-integration repo, we added code to do some parsing on the output of docker-compose up such that the logs from running many services were more easily parseable and accessible from Github Actions. I think we should revisit this work and port it for use in this repository.

[gakonst]

Why would we want to view logs on CI? You can view the logs locally by running docker-compose logs --follow <name of service>

[snario]

Why would we want to view logs on CI? You can view the logs locally by running docker-compose logs --follow <name of service>

I find that it makes it much easier to demonstrate the circumstances that lead to failing test cases in a way that can be linked to over the internet.

This means I can parse through the logs without having to do any local configuration and develop an intuition for a bug.

It also removes all possibility of some local development quirk leading to a false positive bug report or reproduction steps.

Also, when trying to demonstrate a successful example of something working when someone is unsure about it, I can link to an exact snippet of the logs demonstrating some functionality.

In general I'd say viewing CI logs improves a developer team's productivity.

[snario]

Fixed by #1020 and #1098