Prevent users getting stuck with 401s due to too many Auth Tokens

[gsgalloway]

There's some degenerate behavior where once a user has too many API tokens active at once, they start hitting 401 errors from the Warpcast API.

Here's a TG thread showcasing the issue: https://t.me/farcasterdevchat/3441

Here is a script people have been using to wipe all outstanding tokens: https://github.com/davidfurlong/farcaster-auth-tokens/blob/main/revoke-all.ts

We should:

• Reproduce the issue in a test
• Understand the user story that results in this situation. I think it's user's just re-instantiating the MerkleAPIClient class over and over instead of reusing it. Which is a valid thing to want to do, and would surprise a user when it eventually leads to 401s.
• Add in the function to help users wipe all existing auth tokens
• Add code or documentation to prevent users from running into this problem

[github-actions]

🎉 This issue has been resolved in version 5.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀