Package and Class name collision accross modules

[Stewori]

Is your suggestion for improvement related to a problem? Please describe.

I observe at least one package and even class name collision between two JabRef Modules:

org.jabref.cli.ArgumentProcessor exists in jabgui and jabkit and both classes are quite different. They have completely different members, so this is more than just a shadowing hack.
While technically possible, already the package name clash is bad style. So-called split packages are discouraged in the Java module system and can cause unforeseen issues.

From https://dev.java/learn/modules/intro/:

Packages should have a unique origin, so no two modules can contain types in the same package. If they do, this is called a split package, and the module system will refuse to compile or launch such configurations.

Describe the solution you'd like
Please refactor to avoid split packages as it is an unnecessary risk and source of trouble. The earlier this is done, the easier the change will be. I strongly recommend to adjust this before beta phase.

[hexhacker-vee]

/assign-me I can complete this task

[github-actions]

👋 Hey @vrushabhdhoke, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀