Get signal from CI that we are about to be terminated and pro-actively tear down the session #6781
Description
Summary
There are multiple global timeouts in azdo and other CIs. Right now when we reach 90 minute timeout in azdo the job just gets killed, but azdo could set env variable with time when it will start tearing us down, and we could tear down a bit earlier.
There could be different modes to this, ideally the timeout will trigger hang dumps of all processes we know about, + dumps of the console / dotnet test. We probably need at least 5 minutes for that.
There could be more lightweight mode that just triggers teardown, reports tests in progress, generates unsuccessful trx and exits. We probably need less than 1 minute for that.
We would need to be aware of the time of the whole session, e.g. when the limit is set very low (which is hopefully rare), we would not be able to do anything.