The `TEST-UNEXPECTED-FAIL | checks that docIds are unique and increasing | in chrome | Expected 9 to be less than 0` unit test failed in a recent test run in https://github.com/mozilla/pdf.js/pull/13837#issuecomment-890511627, but also locally once for me. Perhaps this goes wrong because the test depends on state that might be mutated if the tests are shuffled?

/cc @Snuffleupagus since this unit test was added in https://github.com/mozilla/pdf.js/pull/13813/commits/b18620ac0f196c6fa5a9e54a53fa6b915e19e843
updatePassword("asdfasdf"); 
          return;
        }
        
        expect(false).toEqual(true);
      };
      const data = await Promise.all([
        passwordNeededCapability.promise,
        passwordIncorrectCapability.promise,
        loadingTask.promise,
      ]);
      expect(data[2] instanceof PDFDocumentProxy).toEqual(true);
      await loadingTask.destroy();
    });
    it("creates pdf doc from PDF file protected with only a user password", async function () {
      const filename = "pr6531_2.pdf";
      const passwordNeededLoadingTask = getDocument(
        buildGetDocumentParams(filename, {
          password: "",
        })
      );
      const result1 = passwordNeededLoadingTask.promise.then(
        function () {
          
          expect(false).toEqual(true);
          return Promise.reject(new Error("loadingTask should be rejected"));
        },
        function (data) {
          expect(data instanceof PasswordException).toEqual(true);
          expect(data.code).toEqual(PasswordResponses.NEED_PASSWORD);