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/client.ts

@@ -289,13 +289,15 @@ export class NextcloudClient {
   }
 
   /**
-   * List every share, over the OCS Sharing API as the mesh's own account. A refused login (401)
-   * makes the account right once (ensureAdminAccount) and asks again; a refusal after that, or a
-   * throttle (429), throws LoginRefusedError, so the caller backs off (novox/hq issue 1253).
+   * List every share, over the OCS Sharing API as the mesh's own account. A refused login (401) or
+   * a throttle (429) makes the account right once (ensureAdminAccount) and asks again; a refusal
+   * or a throttle after that throws LoginRefusedError, so the caller backs off (novox/hq issue 1253).
    */
   async listShares(): Promise<NextcloudShare[]> {
     let res = await this.fetchShares();
-    if (res.status === 401 && !this.accountMadeRight) {
+    // A throttle (429) follows refusals, so it gets the same one repair: the repair goes by occ,
+    // never by a login, and the throttle then wears off under the caller's back-off.
+    if ((res.status === 401 || res.status === 429) && !this.accountMadeRight) {
       await res.text();
       this.accountMadeRight = true;
       this.ensureAdminAccount();