docker_compose_v2* modules: use --progress json for Compose 2.29.0+

[felixfontein]

SUMMARY

Compose 2.29.0 is out: https://github.com/docker/compose/releases/tag/v2.29.0

It features --progress json output (docker/compose#11478), which makes it easier to parse its output.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

docker_compose_v2*

[felixfontein]

The structured output is still somewhat messy, but that's unfortunately not a surprise if you look at how the events are created that the JSON progress dumps (the progress dumping itself is rather dumb, it does not do fancy transforms).

If someone ever wants to rewrite Compose again, I would suggest to start with a proper machine readable output before trying to make it look nice. That will avoid quite some messy progess events from the beginning...

[felixfontein]

(The tests likely didn't run with Compose 2.29.0 in CI so far since the release didn't happen that long ago. In a few days they should actually run with 2.29.0. I locally ran the tests with a self-compiled Compose 2.29.0 and there they seem to pass, if I didn't screw up anything :) )

[felixfontein]

(Arch Linux already has compose 2.29.0 out by now, so it should be used in the tests.)

[felixfontein]

I moved the last commit to #932 and will rebase once that's merged.

[felixfontein]

Hmm I want to test this more thouroughly and potentially add more warnings (like for non-JSON lines).

[felixfontein]

TODO: support tail flag.

[felixfontein]

The failing check is unrelated...