Development: Restructure server code completely into modules

[krusche]

BREAKING

HUGE REFACTORING

This PR completely restructures the server code:

1. Change the package path from de.tum.in.www1.artemis to de.tum.cit.aet.artemis
2. Create module folders to group logical functionality and move files into these modules in the following sub folders
   • config
   • domain
   • dto
   • exception
   • repository
   • service
   • web

Artemis will initially contain the following modules (for now only folders)

1. core (user management, admin, security, config, courses, organization, all remaining features not integrated in another module)
2. assessment (results, grading, scores)
3. athena (connector to the python service Athena to produce automatic feedback)
4. atlas (learning analytics, competencies, learning paths, metrics)
5. buildagent (for programming exercises)
6. communication (conversation, messaging, notifications, emails)
7. exam (exam mode)
8. exercise (basic exercise infrastructure, team exercises, participations, submissions)
9. fileupload (file upload exercises)
10. iris (connector to the pyris service and Iris LLM Chatbot functionality)
11. lecture (lectures, attachment, learning units)
12. lti (connector for external LMS)
13. modeling (modeling exercises, apollon integration, compass)
14. plagiarism (everything related to plagiarism, JPlag integration)
15. programming (everything related to programming exercises, connectors to Gitlab (deprecated), Jenkins, etc.)
16. quiz (everything related to quiz exercises)
17. text (everything related to text exercises)
18. tutorialgroup (everything related to tutorial groups)

Please notice, that this PR is a starting point. Not all files are perfectly sorted into their respective folder (module) yet, however as this is a breaking refactoring that will definitely lead to merge conflicts with all other open branches / PRs, we wanted to finish a good first version. We kindly ask all developers for understanding, this refactoring was necessary and will significantly simplify development in the future.

No actual code was changed, except to fix compile errors or testing issues (e.g. changed visibility, removal of unused code).

This PR will only be tested quickly because with so many changes, it does not make sense to conduct a code review nor can we keep it open for a long time. In case issues are found, please report them and we will fix them in smaller follow-up PRs. However, as we only moved files into different folders, nothing should be broken.

We apologize for inconveniences while resolving merge conflicts!

In a follow-up, we plan to move the server tests into the same folder structure in the test folder.

Checklist

• I tested all changes and their related features with all corresponding user types on a test server.
• I chose a title conforming to the naming conventions for pull requests.
• I strictly followed the server coding and design guidelines.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.