✅ Follow same KDF configuration as account log in when exporting password protected JSON

Instead of PBKDF2 with 600,000 iterations as the default for password protected JSON export, make the default the same as the usual account login. For example, if I have Argon2id when I log in, that should be the case when I export.

I already wrote a PR for this, which got merged a few weeks ago. It should be in an upcoming release.

Thanks again @Quexten for your contribution. Your PR was merged and the changes are included in the 2023.4 release