The basic window interface for the bibliography consistency check

[Donald-0017]

… been created and the next step is now underway.

Describe the changes you have made here: what, why, ...
Link the issue that will be closed, e.g., "Closes #333". If your PR closes a koppor issue, link it using its URL, e.g., "Closes koppor#47".

Mandatory checks

• I own the copyright of the code submitted and I licence it under the MIT license
• 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.

[calixtus]

I don't get it. What is this going to be?

You neither did set up your workspace according to our guide nor did you consider our dev docs and contribution guide. Please take a look at devdocs.jabref.org .

Please explain what this pr should achieve and what issue will be solved.

[subhramit]

Please refrain from contributing to larger open-source projects before going through their contribution guidelines, and also when you have no idea about what you are doing at all. Asking questions is better than blindly using AI.

[subhramit]

No effort at all.

[subhramit]

Closing PR due to excessive and blind AI usage.