chore: Separate eventid column in relationshipitem table [DHIS2-19889]

[enricocolasante]

This is the first of a series of PRs to prepare the tables that have a foreign key to event table for the split into trackerevent and singleevent tables.

In this PR

• Update RelationshipItem hibernate object: split event field into singleEvent and trackerEvent fields and update XML mapping file.
• Split eventid column in relationshipitem table with a flyway script and populate those columns with the correct data (put into singleevent column only single events and same for trackerevent column).
• Update RelationshipItemMapper in web layer to map either a single event or a tracker event to a view event.

Next steps

• Use SingleEvent and TrackerEvent in ProgramNotificationInstance and separate columns in programnotificationinstance table.
• Use SingleEvent and TrackerEvent in ProgramMessage and separate columns in programmessage table.
• Split eventchangelog table to singleeventchangelog and trackereventchangelog tables
• Split event_notes table to singleevent_notes and trackerevent_notes tables
• Split event table to trackerevent and singleevent and update all foreign keys and solve all added TODOs

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

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

[ameenhere]

I think we can group several of these alter table commands together. Which should reduce migration time.
At the very least all add column can happen in a single DDL sql. And drop constraint in a single one and add constraints in a single one.

But I am also wondering about the migration as a whole. This leaves us in an intermediate state right? The overall migration for this initiative is going to be big. So I think we should avoid migrating to intermediate stages. We need to plan this properly.

[ameenhere]

The reason I said intermediate stage is because of this. This ideally should be the single event table eventually right?

Let us discuss how we should plan our migration