Add jwt-parser extension

[watzenare]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

PR Summary

This PR adds a new JWT Parser extension that provides a user-friendly interface for decoding and validating JWT tokens, with features like clipboard detection and color-coded token visualization.

• The extension needs a metadata folder for the screenshots since it has a view command in package.json - see Raycast Documentation
• The screenshots in package.json reference assets/screenshot-1.png but the README shows assets/png/screenshot-1.png - paths should be consistent
• Consider adding subtitle: "JWT Parser" to the command in package.json to match extension title
• Consider wrapping launchCommand in a try-catch block for better error handling
• Consider using showFailureToast from @raycast/utils instead of manual error handling in try-catch blocks

_{💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!}

_{9 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile}

[watzenare]

checked all the comments, I don't know if I have to check anything else to reopen the review