UX: Keystore Import Silently Fails for Files Without .json Extension

[coinselor]

Describe the bug
When importing a keystore using a file, Syrius does not respond if the file does not have a .json extension. Dragging and dropping such a file results in no action being taken, even if the file is a valid keystore file. This behavior can be handled more graciously.

To Reproduce
Steps to reproduce the behavior:

1. Open the Syrius wallet application.
2. Navigate to the keystore import functionality.
3. Drag and drop a valid keystore file that does not have a .json extension.
4. Observe that nothing happens—Syrius does not respond.

Expected behavior
The wallet should recognize valid keystore files regardless of their extension and proceed with the import process.

Actual behavior
The wallet does not respond at all when a keystore file without a .json extension is dragged and dropped.

Workaround
Rename the file to include the .json extension before dragging and dropping it into the import interface.

Desktop (please complete the following information):

• OS: Linux (Desktop)
• Syrius Version: 0.2.2
• Commit hash: c8da966

Additional context
This behavior can cause confusion for users who may not realize that the .json extension is required. Improving the file import process to either recognize valid keystore files regardless of extension or provide an error message to guide the user would enhance the user experience.

The default behavior of most tooling i.e go-zenon/controller/znn-cli is to create a keystore wallet file without a filename extension.