[ID-1897] Improve magic session management

[matthewmuscat]

https://immutable.atlassian.net/browse/ID-1897

Summary

Magic recommends that Passport integrates a little differently, specifically around checking if the magic user is logged in. This also affects how we initialise the magic signer.

Detail and impact of the change

Added

Changed

• Checks if magic user is logged in
• Addresses magic rate limiting issues by reducing the number of calls
• Initialise the magic signer for all RPC calls, not when connectEvm or the IMXProvider is initialised.

Deprecated

Removed

Fixed

Security

Anything else worth calling out?

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a765274. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx affected -t typecheck --parallel=5

✅ Successfully ran 2 targets

• nx affected -t test --parallel=5 --configuration=ci
• nx affected -t lint --parallel=5 --no-error-on-unmatched-pattern

---

Sent with 💌 from NxCloud.

[haydenfowler]

This will have unintended consequences on the passthrough methods when getUser is called. Two scenarios that I can think of:

1. If a token refresh is triggered, then we'll need to wait for that process to resolve before we can pass the method along to the node
2. If a token refresh is triggered and it fails, then this error will be surfaced to the caller

[matthewmuscat]

If a token refresh is triggered, then we'll need to wait for that process to resolve before we can pass the method along to the node

await this.#authManager.getUser(); already awaits the refreshing promise so I think this is fine?

If a token refresh is triggered and it fails, then this error will be surfaced to the caller

Edit: we can just fail silently on this check and let the methods logic handle it with how they see fit.

[matthewmuscat]

ac1424a