nextcloud: repair the account on a throttle too, since a throttle follows refusals (issue 1253)

Right after the delivery the first answer may be Nextcloud's 429, not a 401;
without a repair then the account would never be made and the back-off would
wait out a throttle that cannot end.

modules/nextcloud/test/admin-login.test.ts

@@ -113,15 +113,17 @@ test("a refusal after the repair throws LoginRefusedError once-repaired, short a
   }
 });
 
-// 1253/AC3b: a throttle (429) is a refusal too, and is not met by a repair.
-test("a throttled login (429) throws LoginRefusedError without touching the account", async () => {
+// 1253/AC3b: a throttle (429) follows refusals: it gets the same one repair, and a throttle
+// that stays throws LoginRefusedError.
+test("a throttled login (429) is repaired once and then throws LoginRefusedError", async () => {
   const c = client();
   const occ = standInOcc(true);
   mock.method(c, "occ", occ.impl);
   const f = mock.method(globalThis, "fetch", standInFetch([429]).impl);
   try {
     await assert.rejects(c.listShares(), (err: any) => err instanceof LoginRefusedError && err.status === 429);
-    assert.equal(occ.calls.length, 0);
+    await assert.rejects(c.listShares(), LoginRefusedError);
+    assert.equal(occ.calls.filter((a) => a[0] === "user:resetpassword").length, 1);
   } finally {
     f.mock.restore();
   }