129 entries in the clis, sdks and tealscript category indexes pointed to
files that do not exist in taxonomy/, and 18 subcategories held only
such entries. Remove both so every advertised key can be opened. The
removed entries are recorded locally for re-adding with their files.

* feat(passkey): sign for accounts rekeyed to the passkey account

An account rekeyed to the passkey's address (a legacy ed25519 account moved
to a post-quantum key, keeping its address and history) can now be added to
the passkey wallet and signed for like the passkey's own account.

- addRekeyedAccount(address) checks algod's auth-addr and adds the account
  (error code `not-rekeyed` when it isn't rekeyed to the passkey);
  removeRekeyedAccount(address) drops it; passkeyAddress is the passkey's
  own address.
- The wallet record keeps rekeyed accounts per network (genesis hash, else
  network ID); old records still load, and bad or duplicate entries are
  dropped. Switching networks shows that network's accounts, and a resumed
  session reconciles with the record instead of disconnecting.
- signTransactions signs a transaction whose sender is the passkey's own
  address, a rekeyed account, or an account a txn earlier in the same group
  rekeys to the passkey (only when the group has a group ID). A rekeyed
  account's signatures and its empty signature name the passkey as sgnr.
- signData signs for a rekeyed account; core createStdSignData(data,
  address) refuses an address the wallet doesn't hold (SignDataError 4100).

* fix(core): wait for a rekey to the PQ key that algod hasn't shown yet

Right after addRekeyedAccount, a lagging algod read (no auth-addr yet)
made the manager clear the account's empty signature, and signData
refused it with 4603.

- The manager re-checks an account whose empty signature names its PQ
  key as sgnr while algod shows no rekey, three times 2 s apart, before
  clearing it. A check in between waits for the retry already scheduled.
- createStdSignData asks algod again three times 1 s apart in the same
  case before answering 4603.
- The passkey adapter keeps the active account on sign-in again, so a
  rekeyed account stays active.
- An opt-in LocalNet test (LOCALNET_E2E=1) runs the migration group with
  a real Falcon key: the rekey and the passkey's proof in one group, then
  a transaction and SIWA for the account; a wrong passkey's proof fails
  the group; no proof is signed for a group that rekeys elsewhere.

---------

Co-authored-by: Patrick Bennett <170563+pbennett@users.noreply.github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 9.8.2 to 9.9.0.
- [Release notes](https://github.com/gradle/gradle/releases)
- [Commits](https://github.com/gradle/gradle/compare/v9.8.2...v9.9.0)

---
updated-dependencies:
- dependency-name: gradle-wrapper
  dependency-version: 9.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 9.8.2 to 9.9.0.
- [Release notes](https://github.com/gradle/gradle/releases)
- [Commits](https://github.com/gradle/gradle/compare/v9.8.2...v9.9.0)

---
updated-dependencies:
- dependency-name: gradle-wrapper
  dependency-version: 9.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>