Fix stdout buffer overflow in unit test coverage step

[Copilot]

The unit test coverage step outputs verbose test results to both stdout and a JSON file using tee, causing GitHub Actions stdout buffer overflow.

Changes

• Replace | tee test-result-unit.json with > test-result-unit.json to redirect output directly to file without stdout output

Before:

go test -v -parallel=8 -timeout=3m -run='^Test' -tags '!integration' -coverprofile=coverage.out -json ./... | tee test-result-unit.json

After:

go test -v -parallel=8 -timeout=3m -run='^Test' -tags '!integration' -coverprofile=coverage.out -json ./... > test-result-unit.json

Test results JSON and coverage HTML artifacts continue to be generated and uploaded as before.

Original prompt

Update run test with coverage step in ci.yml to pipe results to a file and not show the output to stdout. The output is too large and overflows the GitHub actions stdout buffer.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.