Support searching references at Google Scholar & Semantic Scholar

[subhramit]

Follow-up to #13153
Closes #12268
Addresses review comments, makes a few enhancements, cleans up some existing code and resolves merge conflicts.

• Unifies URL validation logic across the codebase (URLUtil, URLChecker, LinkedFile).
• Also adds Semantic scholar search (thanks @InAnYan!)

Description copied from the previous PR (and slightly enhanced):

Summary of Changes

This PR adds a new "Search Google Scholar" feature to JabRef, similar to the existing "Search ShortScience" functionality. The feature allows users to quickly search for a selected entry's title in Google Scholar directly from the main table's context menu. The search engines are moved under the "Search..." tab in the right click menu for better organization:

In addition, we make Google Scholar and Short Science links configurable in the Preferences tab, under a new section named "Search Engine URL Templates". One of the comments mentioned, in the issue, that "the URL should be configurable. Reason: We cannot maintain JabRef for all site URLs; and the list of sites might be opinionated." This allows users to customize their URL templates, such as adding additional query parameters like author or strings.

The following shows the link the user is directed to after clicking "Search Google Scholar":

Bullet Pointed List of Changes:

• Added new search Google Scholar option
• Moved search engines to a "Search" sub-menu in right click menu
• Allow "Search Google Scholar" and "Search Short Science" URLs to be configurable in Preferences under the "Search Engine URL Templates" section

Collaborators

@lydia-yan @yoasaaa @brandon-lau0 @FlyJoanne

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.

[InAnYan]

Semantic Scholar has different schema for authors. Instead of single author field, it requires that all authors are separated and an index is added like author[0]=ABC&author[1]=XYZ, but I haven't implemented this properly

[InAnYan]

Gosh I did something with submodules

[InAnYan]

I don't know where I got this java packaging

[InAnYan]

Sorry, but I'm unable to fix the code right now. Hope there are issues only in code formatting

[InAnYan]

But I wonder, can I parse a list of authors by just separating by and? Is and always present if there are several authors? It's not configurable?

[koppor]

But I wonder, can I parse a list of authors by just separating by and? Is and always present if there are several authors? It's not configurable?

This is BibTeX standard. They define the letters and to seperate authors.

Just use org.jabref.logic.importer.AuthorListParser#parse - or did I miss something?

[koppor]

Gosh I did something with submodules

Maybe, you tried out #14124, where we had that submodule for a short time.

[InAnYan]

Maybe, but now everything should be alright with the submodules

[koppor]

I converted to draft, because OpenRewrite fails.

[Siedlerchr]

No system.err println

[InAnYan]

OMG SORRY
I should've deleted this

[InAnYan]

OMG SORRY
I should've deleted this

[koppor]

Our architecture test needs to be adapted.

LOGGER.debug would have been the right replacement 😅

[koppor]

Our architecture test needs to be adapted.

LOGGER.debug would have been the right replacement 😅