`bazel info` is blocked by `bazel build` runs

### Description of the bug:

We do have quite costly `bazel build` run and to check how server is doing we want to run `bazel info` from time to time.

The issue is: if costly `bazel build` is running and Bazel server starting to experience memory pressure, we are unable to see spike of GCs in time.

### 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.

Run `bazel build` and try to run `bazel info` in parallel.

You will see something like
```
bazel info
Another command (pid=605545) is running. Waiting for it to complete on the server (server_pid=598401)...
```

When in reality `info` has no implications on already executed commands since it is a RO operation.

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

RHEL9

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

7.0.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_

### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

_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 reproducing the parallel `bazel build` and `bazel info` commands on RHEL9 with Bazel 7.0.1, then trace how the server schedules these commands. Done means a read-only `bazel info` can inspect server state while a costly build is running instead of waiting for it to complete.

Written by the indexing model from the issue text.