feat: Create note endpoints in tracker [DHIS2-17579]

[enricocolasante]

Added endpoint to create a note for enrollments and events:

• POST tracker/enrollments/{uid}/note
• POST tracker/events/{uid}/note

A new service and a new store using JDBC are created.
The validation applied are:

• Verify that event/enrollment exists
• Verify that user has read access to event/enrollment
• Verify that field value for the note is not empty
• Verify that a note with the same uid does not already exist

Inconsistency between the 2 endpoints
To check that the event/enrollment exists and that the user has all the right permissions we are using services (EnrollmentService.getEnrollment(uid) and EventService.getEvent(uid)) but they do behave differently when an entity without the right permission is accessed:

• EnrollmentService throws a 403
• EventService throws a 404

This is part of a biggest discussion and it will not be fixed here

[muilpp]

@enricocolasante, just for me to understand, why don't we use the importer to create notes as we do for other tracker objects?

[enricocolasante]

@enricocolasante, just for me to understand, why don't we use the importer to create notes as we do for other tracker objects?

We agreed with frontend that would make sense to have an easier way for them to create a single note.
Using the importer for that adds a lot of unnecessary data that they should pass together with the note as we do not allow patch, so they would need to send a payload with the whole enrollment/event just to add a note.
And as well, it is not so good for performance, because we need to validate all that unnecessary data anyway

[ameenhere]

Are notes immutable? Is that why this is done?

[enricocolasante]

Yes, they are immutable

[sonarcloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

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

See analysis details on SonarQube Cloud