`maybe_stress` can take so long to run relative to what we expect for Bazel Essential CI

Problem(s):

It stresses packages affected by the code change. For big code changes, this involves stressing too many tests and it can easily take much more than our future target CI time (15 minutes?).

Tests are stressed for 2 minutes. This means that tests skipped under stress will have to be stressed for 2 minutes each even though they are skipped.

Solution(s):

maybe_stress should be moved to Bazel Extended CI

Changing the 2 minutes timeout to a maximum number of runs (-maxruns) will let when skipped tests are stressed they finish quickly.

Jira issue: CRDB-30048