fix(display): wire --dry-run flag into progress writers

[htoyoda18]

What I did

docker compose --dry-run ... never rendered the DRY-RUN MODE prefix in progress output, on any of the three renderers.

The pieces are there but nothing connects them:

TTY: termWriter has a dryRun field and tty_layout.go prefixes every row with it, and WithDryRun() exists as a TermOption — but nothing ever passes that option, so it is always false.
plain / json: plainWriter/jsonWriter both have a dryRun field used at render time, but neither Plain() nor JSON() accepts a value for it, so it is always false too.
This wires the already-parsed --dry-run flag through selectEventProcessor to all three:

TTY: passes the existing display.WithDryRun() option — cmd/display/tty.go itself is unchanged.
plain / json: adds a dryRun bool parameter to the two constructors.
Tests: the TTY case asserts on the rendered frame (the marker actually reaches the output) rather than on the field; plain_test.go / json_test.go cover the other two renderers.

Note: this PR was originally written before the tty.go model/layout/screen refactor and has been rebased and reworked on top of it. The earlier version added a dryRun parameter to display.Full(); it now uses the WithDryRun() option that the refactor introduced, which keeps tty.go untouched.

Related issue
N/A

(not mandatory) A picture of a cute animal, if possible in relation to what you did
🐈

[htoyoda18]

Hi @ndeloof — this fixes the FIXME you left in cmd/display/tty.go (dryRun field was never wired up across the tty/plain/json progress writers, so --dry-run never showed the DRY-RUN prefix in progress output). I've since rebased on top of your PersistentPreRunE refactor and the display.Mode resolution changes, so it should apply cleanly. Would appreciate a review when you have a chance — thanks!

[htoyoda18]

Hi @ndeloof @glours 👋 Just a friendly nudge on this one too — it's been a couple of weeks with no review yet. Happy to address anything if you get a chance to take a look. Thanks!

[htoyoda18]

Hi @ndeloof @glours 👋 Gentle nudge on this one when you have a moment.

Rebased on the new tty model/layout/screen split, and reworked along the way:
--dry-run never reached the progress writers, so the DRY-RUN marker was never
rendered. TTY now just gets the existing display.WithDryRun() option (so
tty.go itself is untouched), and Plain/JSON take a dryRun param.

Verified against a real daemon with a 2-service project:

• plain: Image alpine:3.20 Pulling → DRY-RUN MODE - Image alpine:3.20 Pulling
• json: "dry-run":true now present
• tty: ✔ DRY-RUN MODE - Network xxx_default Created
• without --dry-run: no prefix and no dry-run field, so no regression

If you don't think this is worth merging, just let me know and I'll close it.
Thanks!