test: make blob desiredSize assertion robust

The blob stream pull continuation runs with setImmediate(), while the
test checks desiredSize from a timer. Depending on platform scheduling,
the stream may or may not have queued the next 5-byte chunk yet.

Accept both valid intermediate states to avoid flaky failures.

Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Assisted-by: openai:gpt-5.5
PR-URL: #64106
Refs: https://github.com/nodejs/reliability/issues?q=sort%3Aupdated-desc%20%22parallel%2Ftest-blob%22
Reviewed-By: Filip Skokan <panva.ip@gmail.com>

Author: trivikr

test/parallel/test-blob.js

@@ -354,8 +354,10 @@ assert.throws(() => new Blob({}), {
   assert(!done);
   setTimeout(common.mustCall(() => {
     // The blob stream is now a byte stream hence after the first read,
-    // it should pull in the next 'hello' which is 5 bytes hence -5.
-    assert.strictEqual(stream[kState].controller.desiredSize, 0);
+    // it may have pulled in the next 'hello' which is 5 bytes hence -5.
+    // The ordering of this timer and the stream's setImmediate() pull
+    // continuation can vary across platforms.
+    assert([0, -5].includes(stream[kState].controller.desiredSize));
   }), 0);
 })().then(common.mustCall());