Update keepassxc extension

[pabroux]

Description

Hello 👋🏻,

⚠️ Still the author here and not the contributor (raycastbot still incorrectly notifies the former author zkytech).

Here is what I've done:

Changed

• Use a global info message about security when the database is locked.
• Update screenshot about the database being locked.
• Use more explicite error messages when unable to exececute the keepassxc-cli command.

Fixed

• Use a correct link for the KeePassXC image in the README.

Removed

• The test guide.

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]

Thank you for your contribution! 🎉

🔔 @zkytech you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

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

[greptile-apps]

PR Summary

This PR updates the KeePassXC extension with improved error messaging, documentation changes, and dependency updates.

• There's a spelling error in CHANGELOG.md: "explicite" should be "explicit" in the error message description
• The error message in keepass-loader.ts removes specific error codes which could make debugging harder, consider keeping detailed errors in logs
• The security message in unlock-database.tsx is now consolidated but could be more prominent given its importance
• Dependencies @raycast/api and @raycast/utils have been updated to newer minor versions
• The README image source now correctly uses repository-relative paths instead of external URLs

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

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

[LitoMore]

Still the author here and not the contributor (raycastbot still incorrectly notifies the former author zkytech)

It's because the mapping data in the raycast2github.json is wrong. We might need to fix it manually:

extensions/.github/raycast2github.json

Line 1830 in 201037d

"pabroux": "zkytech",

[pabroux]

Still the author here and not the contributor (raycastbot still incorrectly notifies the former author zkytech)

It's because the mapping data in the raycast2github.json is wrong. We might need to fix it manually:

extensions/.github/raycast2github.json

Line 1830 in 201037d

"pabroux": "zkytech",

I've done a commit to change the mapping 4b6df1b.

Edit: 381a6db to merge conflicts.