Fix some fetcher tests

[calixtus]

refs #6369

• Change in CHANGELOG.md described (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 documentation: Is the information available and up to date? If not created an issue at https://github.com/JabRef/user-documentation/issues or, even better, submitted a pull request to the documentation repository.

[Siedlerchr]

I think the INSPIRE test can also be fixed, seems like the bib item changed

[calixtus]

The INSPIRE test leaves me clueless. The text is exactly the same. Maybe it's about the line seperators? I was unable to debug the test myself. Can you maybe take a look at it, @Siedlerchr ?

[Siedlerchr]

For inspire change the line in the second entry to this:
article.setField(StandardField.JOURNAL, "Nucl. Phys. B");
without the double back slashes

[calixtus]

@Siedlerchr and @tobiasdiez , could you do me a favor and take a look on the buildinfo stuff, i'm not sure if I did that right and i'm unable to debug that. According to the test log, instead of the api key the IEEE fetcher only recieves three asterisks from the build script. Is this normal? Did I do something wrong?

[koppor]

The test log does not output the API keys, it just outputs starts. This is perfectly OK.

[calixtus]

This PR is done for now and should fix all the fetcher tests, except IEEE fetcher, which depends most likely on a new api key.

[Siedlerchr]

So we now only have MrDlib and IEEE not working

[calixtus]

Strange, MrDlib tests ran through an hour ago without complaining...