Improve AI preferences UI and templates

[InAnYan]

Closes https://github.com/JabRef/jabref-issue-melting-pot/issues/822.

Changes:

• AI preferences:
  • Add explanation to AI features.
  • Move additional features to miscellaneous.
  • Hide expert settings, if their modification is turned off.
  • Add button to reset only one template.
• AI templates:
  • Now each AI functionality piece is represented by 2 templates - one for system message, other for user message. This is more modern and robust style.
  • Added customizable prompt for plain citation parsing.

UI screenshots of preferences:

Hidden expert settings:

Expanded expert settings:

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• [/] Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (if change is visible to the user)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[InAnYan]

I could make 2 PRs, one for AI preferences, other for templates, but that would introduce breaking changes.

I'm too lazy, so I made 1 PR. The only problem with this approach is that we can discuss AI preferences UI look for too long

[InAnYan]

Oh, I forgot about localization.

(I will sleep now)

[subhramit]

Conflicts probably arose here because of my last PR. I'll push a commit to resolve

Took the opportunity to fix localization and checkstyle as well

[subhramit]

Committing thilo's suggestion, in case we forget later

[jabref-machine]

Your pull request needs to link an issue correctly.

To ease organizational workflows, please link this pull-request to the issue with syntax as described in https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue:

Linking a pull request to an issue using a keyword

You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message.

Examples

• ✅ Fixes #xyz links pull-request to issue. Merging the PR will close the issue.
• ✅ Fixes https://github.com/JabRef/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
• ✅ Fixes https://github.com/Koppor/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
• ❌ Fixes [#xyz](https://github.com/JabRef/jabref/issues/xyz) links pull-request to issue. Merging the PR will NOT close the issue.

[subhramit]

(for later) @koppor is {{matrix.module}} intended here after the recent changes?