Streamline test output

[koppor]

Our fetcher tests output the test results twice:

> Task :fetcherTest
org.jabref.logic.importer.fetcher.ACSTest

  Test findByDOI() FAILED

  org.opentest4j.AssertionFailedError: expected: <Optional[https://pubs.acs.org/doi/pdf/10.1021/bk-2006-STYG.ch014]> but was: <Optional.empty>


ACSTest > findByDOI() FAILED
    org.opentest4j.AssertionFailedError: expected: <Optional[https://pubs.acs.org/doi/pdf/10.1021/bk-2006-STYG.ch014]> but was: <Optional.empty>
        at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)

This was unreadable.

---

We have the plugin gradle-test-logger-plugin enabled for that. Today, I found the solution (refs radarsh/gradle-test-logger-plugin#252 (comment)).

Configure the plugin correctly :)

---

New output (excerpt)

  Test findManyEntries() FAILED (1.2s)

  org.jabref.logic.importer.FetcherException: Error while fetching from Google Scholar


org.jabref.logic.importer.fetcher.GrobidCitationFetcherTest

  grobidPerformSearchCorrectResultTest(String, BibEntry, String)

    Test example1 FAILED (42.2s)

    org.opentest4j.AssertionFailedError: expected: <[@article{-1,
      author = {Derwing, Tracey and Rossiter, Marian and Munro, Murray},
      date = {2002-09},
      doi = {10.1080/01434630208666468},
      journal = {Journal of Multilingual and Multicultural Development},
      month = {9},
      number = {4},
      pages = {245-259},
      publisher = {Informa UK Limited},
      title = {Teaching Native Speakers to Listen to Foreign-accented Speech},
      volume = {23},
      year = {2002},
      _jabref_shared = {sharedId: -1, version: 1}
    }]> but was: <[]>

---

Follow-up to #5676.

---

The output of org.jabref.logic.l10n.LocalizationConsistencyTest#findMissingLocalizationKeys is still showing instructions (in IntelliJ)

DETECTED LANGUAGE KEYS WHICH ARE NOT IN THE ENGLISH LANGUAGE FILE
PASTE THESE INTO THE ENGLISH LANGUAGE FILE

%0\ matches\ the\ term\ <b>%1</b>=%0 matches the term <b>%1</b>

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.

[github-actions]

The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build.

[Siedlerchr]

lgtm