Fix: Refactor BibtexParser to use ranges of articles and work with them in the LSP instead of string matching

[palukku]

Closes palukku#42 & Closes palukku#45 & Closes palukku#50

In #13746 the ranges of the fields and entries it self got added now the lsp utilizes these ranges instead of simple string matching.

Also aliases are now handled so if there the error occurs on an alias field the alias is also correctly detected.

Steps to test

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.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨