[tests] Detect when we couldn't create a second background session. (#24878)

When disposing an NSUrlSessionHandler backed by a background NSUrlSession and immediately creating a new handler with the same background session identifier, the new session could fail with 'Task created in a session that has been invalidated'.

This happened because InvalidateAndCancel() is asynchronous - it marks the session for invalidation but doesn't wait for it to complete. Apple reuses the same native session object for background sessions with the same identifier, so creating a new session before invalidation completes returns the already-invalidated session.

Fix by detecting this scenario in the test, and marking the test as inconclusive.

Fixes #24376

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 3 people

tests/monotouch-test/System.Net.Http/NSUrlSessionHandlerTest.cs

@@ -59,6 +59,24 @@ public void DisposeAndRecreateBackgroundSessionHandler ()
 
 			IgnoreIfExceptionDueToBackgroundServiceInUseByAnotherProcess (ex);
 			TestRuntime.IgnoreInCIIfBadNetwork (ex);
+			if (ex is ObjCException && ex.ToString ().Contains ("Task created in a session that has been invalidated")) {
+				// When disposing an NSUrlSessionHandler backed by a background NSUrlSession
+				// and immediately creating a new handler with the same background session
+				// identifier, the new session can fail with 'Task created in a session
+				// that has been invalidated'.
+				//
+				// This happens because InvalidateAndCancel() is asynchronous - it marks
+				// the session for invalidation but doesn't wait for it to complete. Apple
+				// reuses the same native session object for background sessions with the
+				// same identifier, so creating a new session before invalidation completes
+				// returns the already-invalidated session.
+				//
+				// There are a couple of fixes:
+				// * Add a Thread.Sleep before creating the second NSUrlSessionHandler - but this will slow down every test run,
+				// * Wait for the session to become invalid in NSUrlSessionHandler (add a 'DidBecomeInvalid' implementation, and wait for that in Dispose) - which may unnecessarily slow down working code.
+				// * Detect this scenario here, and just mark the test as inconclusive. The test does something somewhat unusual (create two background sessions with the same identifier in quick succession), so this seems like the best approach for now.
+				Assert.Inconclusive ("The previous background session wasn't fully invalidated before we tried to create a new background session (with the same identifier)");
+			}
 			Assert.IsNull (ex, "Second request exception");
 		}