Adding --no-password option to CLI

[louib]

I also added tests for the --key-file option, which was
untested.

Closes #1873

@phoerious this is one the reasons why I opened #1873 last week. This way adding features to unlockDatabase is normalized across the CLI commands.

Type of change

• ✅ Bug fix (non-breaking change which fixes an issue)
• ✅ Refactor (significant modification to existing code)
• ✅ New feature (non-breaking change which adds functionality)
• ✅ Breaking change (fix or feature that would cause existing functionality to change)
• ✅ Documentation (non-code change)

Description and Context

Testing strategy

Local testing + unit tests.

Checklist:

• ✅ I have read the CONTRIBUTING document. [REQUIRED]
• ✅ My code follows the code style of this project. [REQUIRED]
• ✅ All new and existing tests passed. [REQUIRED]
• ✅ I have compiled and verified my code with -DWITH_ASAN=ON. [REQUIRED]
• ✅ My change requires a change to the documentation, and I have updated it accordingly.
• ✅ I have added tests to cover my changes.

[droidmonkey]

Tests are failing for Windows

[louib]

@droidmonkey should be good now!

[arvinep]

Thanks for this feature.
I have difficulty to find the documentation as I try to figure how to use it.

Trying to use --no-password is failing:

$ keepassxc-cli clip --no-password -k /home/kepassxc_key /home/keepassxc.kdbx <Entry>
Error while reading the database: Invalid credentials were provided, please try again.
If this reoccurs, then your database file may be corrupt.

While skipping --no-password and entering the password works perfectly fine.

$ keepassxc-cli clip -k /home/kepassxc_key /home/keepassxc.kdbx <Entry>
Insert password to unlock /home/keepassxc.kdbx: 
Entry's password copied to the clipboard!

[droidmonkey]

--no-password is meant for a database that does not have a "password" component of its master key. If you have to enter a password, you do not meet the requirements for --no-password.