Excessive retries in test workflow environment

When testing an activity that constantly fails (cannot recover from the failure) and has a large scheduleToClose timeout set (like days/months), or does not have one set at all
the testing framework will keep retrying in some cases thousands of times.

Asking to add a feature that in those edge cases to not retry, but skip time so the excessive retries are avoided in tests.

To reproduce you can have a workflow which calls a single activity with activity options setScheduleToCloseTimeout set to 5 days for example. Set the activity to fail with for example:
throw Activity.wrap(new Exception("oops"));

in test you will see that it performs over 4K retries before timing out.

Start by reproducing the issue in the testing framework with a workflow calling one activity, a five-day schedule-to-close timeout, and an activity that throws Activity.wrap(new Exception("oops")). Trace the retry and time-skipping behavior, then verify that the excessive retries are avoided while the test still reaches its timeout outcome.