feat: Remove old TEA change log [DHIS2-18477]

[muilpp]

This PR removes the old TEA change log endpoint, service, and store.
While working on this, I realized a few things:

• Initially, my idea was to keep the TEA change log delete method, similar to what we did for event change logs. This way, when a TE is deleted, we could also delete all related change logs from the new table and the old one. However, the problem with this approach is that if the implementation decides to drop the old table, the project will no longer compile because the Hibernate mapping won't find that table. While this compilation error could be resolved by using JDBC instead, it would lead to runtime errors, which doesn't improve the situation. For this reason, I decided to remove the method altogether, meaning no change logs will be deleted from the old TEA change log table anymore. The same applies to event change logs. These two tables are completely the responsibility of the implementation.
• I'm using plainValue for TEA instead of value to ensure that if the value is encrypted, the encrypted value doesn’t end up in the change log table.
• When manually merging two entities, the deduplication service was adding a DELETE change log entry on behalf of the duplicated TE. That TE was then deleted along with all its related change logs, including the one just created. I removed the step where that DELETE change log entry is created.
• TrackedEntityAuditService and TrackedEntityAuditStore should not be deprecated. This was probably due to confusion caused by the inconsistent naming between "change log" and "audit."
• DefaultTrackedEntityAttributeValueService.updateTrackedEntityAttributeValue was only used in tests, so I am removing it as well.

[enricocolasante]

I always get confused when we talk about audit.
Is TrackedEntityAudit really used by someone? Maybe we can ask one more time, hopefully last time, to Morten to be sure it is needed.
It seems to me that it is just auditing when something it is DELETED and randomly auditing when something is READ.

[enricocolasante]

If this is not deprecate, should be moved outside deprecated package?

[enricocolasante]

I think we need to add this removal somewhere in the release-notes

[muilpp]

We do, it's my next and hopefully final step when it comes to change logs.

[muilpp]

I always get confused when we talk about audit. Is TrackedEntityAudit really used by someone? Maybe we can ask one more time, hopefully last time, to Morten to be sure it is needed. It seems to me that it is just auditing when something it is DELETED and randomly auditing when something is READ.

I don't know if someone is using the audit feature, I'll contact Morten to clarify that. Until then, I think it should not be deprecated. The confusion probably started because this interface was called TrackedEntityChangeLogService before we realized it was actually about auditing, which is likely why it got deprecated.

[sonarcloud]

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 SonarQube Cloud