More control around --keep_going

### Description of the bug:

We use --keep_going to collect a full set of errors that can be fixed in one go. --keep_going could be improved to allow this set of issues to be collected better:

* Allow a max errors limit to be supplied - after reaching this number of failing targets, stop.

This would allow a good set of failing targets to be collected, whilst not allowing a large monorepo build with some systemic issue to spend a long time failing everything.

### Which category does this issue belong to?

Core

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

_No response_

### Which operating system are you running Bazel on?

windows

### What is the output of `bazel info release`?

7.3.1

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

_No response_

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start by tracing Bazel's --keep_going option handling and how failing targets are counted. Determine where a maximum error limit belongs, then add coverage for stopping after the configured number of failing targets; done means the limit works without changing existing --keep_going behavior.

Written by the indexing model from the issue text.