Avoid parsing skipped range requests in ChunkedStreamManager (PR 10694 follow-up)

[Snuffleupagus]

While we don't dispatch the actual range request after PR #10694 we still parse the returned data, which ends up being an empty ArrayBuffer and thus cannot affect the ChunkedStream.prototype._loadedChunks property.
Given that no actual data arrived, it's thus pointless[1] to invoke the ChunkedStreamManager.prototype.onReceiveData method in this case (and it also avoids sending effectively duplicate "DocProgress" messages).

---

[1] With the possible exception of disableAutoFetch === false being set, see

pdf.js/src/core/chunked_stream.js

Lines 499 to 517 in f24768d

	// If there are no pending requests, automatically fetch the next
	// unfetched chunk of the PDF file.
	if (!this.disableAutoFetch && this._requestsByChunk.size === 0) {
	let nextEmptyChunk;
	if (stream.numChunksLoaded === 1) {
	// This is a special optimization so that after fetching the first
	// chunk, rather than fetching the second chunk, we fetch the last
	// chunk.
	const lastChunk = stream.numChunks - 1;
	if (!stream.hasChunk(lastChunk)) {
	nextEmptyChunk = lastChunk;
	}
	} else {
	nextEmptyChunk = stream.nextEmptyChunk(endChunk);
	}
	if (Number.isInteger(nextEmptyChunk)) {
	this._requestChunks([nextEmptyChunk]);
	}
	}

however that never happens when streaming is being used; note

pdf.js/src/core/worker.js

Lines 237 to 238 in f24768d

	// We don't need auto-fetch when streaming is enabled.
	pdfManagerArgs.disableAutoFetch ||= fullReader.isStreamingSupported;