Add logs to services on backend for future frontend use and display.

[pdPinho]

Issue

Closes #194

Reason for this change

Debugging and monitoring what was happening in our backend was quite difficult and vague due to relying on normal error logs. This PR aims to add some logs to the services which will help us understand what, how and when something happened. On top of that we will also be capable of visualizing and easily monitor these logs (and monitors) on the frontend in the upcoming feature for the dashboard.

Description of changes

• Deleted unnecessary files such as unused ENUMs;
• Added logs to most services;
• Removed unused code from services;
• Added javadoc comments to services;
• Changed some get services behavior for consistency.

Description of how you validated changes

Ran docker compose up and local unit tests.

Checklist

• [X] I have tested my changes locally.
• [ ] I have updated the documentation to reflect my changes.
• [ ] I have added/updated unit tests (if applicable).
• [X] My code adheres to the CONTRIBUTING GUIDE

Aditional Information

The logs are by default being created with the user admin. This has to be changed in the future.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
1 Security Hotspot
25.8% Coverage on New Code (required ≥ 80%)
B Security Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[pdPinho]

• Security hotspot is due to open CORSORIGIN (*); This will be fixed once the website is up and running.
• Low coverage test range comes from Template, TemplateGroup and Rule. These should be addressed at a later stage.