chore: refresh gator permissions map after revocation state change

[MoMannn]

Explanation

What is the current state of things and why does it need to change?

Currently, when a revocation transaction changes state (confirmed, failed, or dropped), the GatorPermissionsController only submits the revocation (on confirmation) or cleans up listeners. However, it doesn't refresh the local permissions map to reflect the updated state from the permissions provider.

This creates a potential inconsistency where:

• On confirmation: After successfully submitting a revocation, the local permissions map may still contain stale data until the next manual refresh
• On failure/drop: When a transaction fails or is dropped, the permission that was pending revocation remains active, but our local state doesn't reflect this

This means the UI could display outdated permission states, leading to confusion or incorrect actions by users.

What is the solution your changes offer and how does it work?

This PR introduces automatic permission refresh after revocation transaction state changes:

1. Added a refreshPermissions helper function that calls fetchAndUpdateGatorPermissions({ isRevoked: false }) with fire-and-forget semantics, catching and logging any errors to prevent them from blocking cleanup operations.

2. Integrated refresh into transaction handlers:

   • Confirmed transactions: After submitting the revocation (successfully or not), refresh permissions in a .finally() block to ensure the map reflects the new revoked state
   • Failed transactions: Refresh permissions after cleanup to restore any permissions that were pending revocation but never executed
   • Dropped transactions: Same as failed - refresh to ensure the permissions map is accurate

3. Error handling: The refresh operation is intentionally fire-and-forget with error logging, ensuring that refresh failures don't interfere with the cleanup flow or cause user-visible errors.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Automatically refreshes the gator permissions map after revocation transactions are confirmed, failed, or dropped, with accompanying tests and changelog updates.

• Controller (src/GatorPermissionsController.ts):
  • Add refreshPermissions helper to call fetchAndUpdateGatorPermissions({ isRevoked: false }) after revocation state changes.
  • On transactionConfirmed: call submitRevocation then refresh in .finally(...).
  • On transactionFailed and transactionDropped: cleanup and refresh permissions.
  • Add error-logged, fire-and-forget refresh flow.
• Tests (src/GatorPermissionsController.test.ts):
  • Import flushPromises and use it to await async flows.
  • Update tests to assert refresh via permissionsProvider_getGrantedPermissions with { isRevoked: false } after confirmed/failed/dropped states.
  • Add tests for refresh error handling on failed/dropped paths; adjust test names accordingly.
• Changelog:
  • Note addition: refresh permissions map after revocation state change.

^{Written by Cursor Bugbot for commit 27160c3. This will update automatically on new commits. Configure here.}

[mj-kiwi]

LGTM

[jeffsmale90]

LGTM! One very inconsequential nit

[jeffsmale90]

Noice