Fix NoSuchElementException in ThreeWayMerge dialog

[HoussemNasri]

Fixes #13673

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• I checked the user 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 updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

[subhramit]

Just openrewrite is left i think

[subhramit]

Nope, the logs seem like its that odd prolog error that keeps happening
Let me try merging main once

[subhramit]

No change, the error seems to be XML Parse Exception for:
jabref/jablib/src/main/resources/csl-styles/oscola-journal-abbreviations.csl and jabref/jablib/src/main/resources/csl-styles/eu-interinstitutional-style-1st-edition.csl (instead of literatura.csl that appeared in the past).
Under Task :jablib:extractMaintainers

[Siedlerchr]

Task :rewriteDryRun
Recipe validation error in org.jabref.config.rewrite.cleanup.recipeList[71] (in file:/home/runner/work/jabref/jabref/rewrite.yml): recipe 'org.openrewrite.java.testing.cleanup.AssertLiteralBooleanToFailRecipe' does not exist.

[trag-bot]

Method duplicates logic from checkValue() which violates DRY principle. Should refactor to reuse existing validation logic to prevent maintenance issues.