test: stabilize view model golden output

[jackwalkerlabs]

Closes #1746.

TestViewModel compares the complete terminal output against golden files, but its program uses the default 60 FPS renderer ticker. Under the race detector with GOMAXPROCS=1, that ticker can flush an intermediate frame before Quit is handled, making valid renderer timing change the escape-sequence ordering.

Run this short golden-output test at 1 FPS so the asynchronous renderer tick stays outside the test window. Production behavior is unchanged, and the existing golden files remain unchanged.

Validation:

• go test -race -count 1000 -cpu 1 -run TestViewModel ./...
• go test -race -count 4 -cpu 1,4 ./...
• go run github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.9.0 run
• git diff --check

[xevrion]

Thanks for picking this up. I'd proposed this fix in #1746 and had it on a branch, so I'm glad either way as long as it lands.

One suggestion for the PR body: it's worth stating explicitly that the golden files are unchanged. That's the part that shows the recorded ordering was always correct and only the timing was unstable, which makes the fix easier to review than if it came with regenerated testdata.

[jackwalkerlabs]

Good point—updated the PR body to state explicitly that the golden files are unchanged. Thanks for confirming the direction.