[10.0.0] fix: Format target counts in Found summaries (#31716) (#32215) ### Description Use `StringUtil.formatCount` in the `Found` summaries for builds and tests. Counts of 10,000 or more now include commas, matching other CLI messages. Adds seven regression tests covering build-only, test-only, and mixed summaries at the formatting boundary. All seven tests and the existing `ProgressReportingTest` pass. ### Motivation Fixes https://github.com/bazelbuild/bazel/issues/31718 https://github.com/bazelbuild/bazel/issues/32210 These messages were missed in #28922, resulting in inconsistent output: ```text INFO: Analyzed 380,363 targets ... INFO: Found 380363 targets... ``` The second message now reads `Found 380,363 targets...`. Reported in https://github.com/bazelbuild/bazel/pull/28922#issuecomment-6070426661. ### Build API Changes No ### Checklist - [x] I have added tests for the new use cases (if any). - [x] I have updated the documentation (if applicable). No documentation changes needed. ### Release Notes RELNOTES: Target counts of 10,000 or more in the "Found" summaries for builds and tests now include comma separators, matching other CLI messages.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
