Hotfix: Always create a PR for updating journal lists

[koppor]

Our .mv file gets updated too often. I don't see, why.

Thus adapting the workflow not to commit and push, but always to create a PR.

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.

[Siedlerchr]

Apparently there were merge conflicts in the csl file

[koppor]

PR created at #10139. Thus, works.

[koppor]

I did not update that file. Don't know, why this appears now - and not in #10136

[github-actions]

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

[Siedlerchr]

I think we merged the conflict checker after the csl update

[koppor]

I think we merged the conflict checker after the csl update

This is why I wonder. If it is NOW a conflict in this PR (based on latest main), there should have been a conflict when the checker was added (also based on the latest main back then).

[Siedlerchr]

Or maybe it was the other way round