dev-stack.sh progress output, and a stale pnpm version in the README

[gabitoesmiapodo]

User story / Problem statement

Leftovers from a review of the installer: BootNodeDev/dAppBoosterInstallScript#16

./scripts/dev-stack.sh up prints a ==> line for each step, but never says how many steps there are or how long one has been running. The first run pulls about 10 GB of images, so a normal wait looks the same as a hang. The output is ANSI-coloured prose, which a script cannot read.

Separately, README.md line 8 asks for pnpm 11.22.0 while package.json pins pnpm@11.24.0.

Expected outcome

Someone running up can tell how far along it is. A script running it can read the same progress without parsing colours. The README names the tools it needs without pinning a version that goes stale.

Acceptance criteria

Human output:

• Each ==> line shows its position, such as [3/7]
• The two long waits print elapsed time while they run
• The closing Stack is up: line reports the total time
• Colour turns itself off when stdout is not a terminal
• The output stays readable when piped to a file

Machine output:

• up --json prints one JSON object per line, flushed as each step happens
• Each object carries the step name, its position, the total, a status and the seconds elapsed
• A failed step prints a final object with the status and the message, so the stream never just stops
• --json sends the machine stream to stdout and leaves the human log on stderr
• up --quiet prints errors and the closing Stack is up: block, nothing else
• --json and --quiet together are either defined or rejected with a message

README:

• The requirements list says pnpm, with no version

Technical notes

The long waits are wait_for_http (300 s, LocalNet JSON API) and wait_for (60 s, dApp dev server). Both already loop once a second. Colour comes from log, warn and die, which are the three places a format switch has to reach.