Configure the time it take for `printStackTracesIfJvmExitHangs` to dump

### Description of the feature request:

currently, it's 5 minutes. however, we have cases where the test setup is longer than that so if we could either configure a longer timeout or opt out of this feature in a test

### Which category does this issue belong to?

Configurability

### What underlying problem are you trying to solve with this feature?

some of my test runs are cluttered with stacktraces. it's hard to understand the log.
also, imagine the build system of a company: the tests takes more time to finish, so everyone is slowed down or we need more resources, and sometimes the output is large enough to behave badly in CI systems

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

Mac OS / Linux

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

release 6.1.2

### 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 master; git rev-parse HEAD` ?

_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 locating the implementation of `printStackTracesIfJvmExitHangs` and the current five-minute timeout, then inspect how Bazel exposes configuration for test execution. Done means callers can configure a longer timeout or opt out, with coverage for the selected behavior and reduced unwanted stack-trace output.

Written by the indexing model from the issue text.