Escape quotes in import command

[LyzardKing]

This updates the python script to keep the double quotes
(or to not fail at least) if passed on the cli by the extension.
if i call jabref --importBibtex """some citation "with quotes" """
the triple quotes should resolve it properly.

---

• Change in CHANGELOG.md described
• Tests created for changes
• Manually tested changed features in running JabRef
• Screenshots added in PR description (for bigger UI changes)
• Ensured that the git commit message is a good one
• Check documentation status (Issue created for outdated help page at help.jabref.org?)

[koppor]

I don't know about the differences between 'string' and "string" in python. The code looks consistent now.

[LyzardKing]

The auto formatter only sets double quotes by default..
Single and double quotes are exactly the same.
The only part where I need the single quotes is the cmd, so I can use double quotes in the command without using an escape.
I could set all the quotes to single then.. it should be fine

[LyzardKing]

I think that the best practices (unless we prefer a different approach)
is to use double quotes (more standard) if possible, and single quotes only if not possible,
like in the cmd string.
Then I updated the log functions to all use fstrings, so they are more readable and up to date

[LyzardKing]

Should I add the changes to this to the changelog as well?
I guess it's a small change, but a larger changelog entry for the import change can be added, with a reference to the different PRs..
The screenshot doesn't apply, as does the documentation status(?)

[koppor]

In this case, there IMHO is no CHANGELOG entry necessary. You are right with the other things. -- Thank you for being active!

FYI: checklist discussion at #5587