Update lucene branch

[LoayGhreeb]

This is a follow-up to #8963. We target main, because targetting luceneSearchBackend leads to much more "unrelated" commits.

Mandatory checks

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• 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.

[koppor]

• Fix https://github.com/JabRef/jabref-issue-melting-pot/issues/12

[koppor]

I triggered a merge. Maybe, the tests will work then again? - I also hope that we will see a build at https://builds.jabref.org/pull/11326/.

[koppor]

This branch is coming from an external repository; therefore, no secrets for build upload are present. Testers need to compile for themselves on the local machine.

Depending on the issues, we either work towards a quick merge into main - or create a branch inside the JabRef main repository (and maybe create a new pull request).

[LoayGhreeb]

This branch is coming from an external repository; therefore, no secrets for build upload are present. Testers need to compile for themselves on the local machine.

Depending on the issues, we either work towards a quick merge into main - or create a branch inside the JabRef main repository (and maybe create a new pull request).

I will create a new branch and a new pull request. This PR should be merged after the search floating mode PR is merged.