Migrate fetchers to Search.g4 ANTLR parser.

[turhantolgaunal]

Closes #13607

• Changed inherited fetcher classes to use ANTLR generated classes instead of lucene libraries.
• Changed ACMPortalFetcher.java logic for transforming the parsed syntax to URL

TO DO:

• Replace the logic in other fetcher classes to transform the parsed nodes into URL calls.
• Modify other fetcher classes to correctly override changed inherited functions.

Steps to test

Using the Search.g4 syntax for searching on the web with different options.

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (if change is visible to the user)
• 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.

[calixtus]

Great start, to me it looks like your on the right track.

[trag-bot]

The Javadoc comment merely restates what is obvious from the parameter name and type. It should provide additional information about the expected format or constraints of the query list.

[jabref-machine]

JUnit tests of jabkit are failing. You can see which checks are failing by locating the box "Some checks were not successful" on the pull request page. To see the test output, locate "Source Code Tests / Unit tests (pull_request)" and click on it.

You can then run these tests in IntelliJ to reproduce the failing tests locally. We offer a quick test running howto in the section Final build system checks in our setup guide.