Fix: fix duplicate entry during indexation (alternative approach)

[Koc]

📝 Summary

This is alternative approach to fix #1886, #2405. Even after #2451 we observe tons of logs on PostgreSQL side related to duplication. In this PR this logs are gone

🏁 Checklist

• Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
• Sign-off message is added to all commits
• Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests
• Documentation (README or documentation) has been updated or is not required

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI tools
• The AI-generated content was reviewed, comprehended and tested by a human

[mejo-]

@Koc thanks, this looks very promising. I didn't even know about insertIgnoreConflict(). Could you adjust VersionsBackend.php as well and replace the try/catch with it?

[Koc]

@mejo- sure, give me few days and I will finalize current PR

[mejo-]

Thanks @Koc. One question/comment.

[mejo-]

Can you elaborate on why you introduced this trait instead of just using $this->db->insertIgnoreConflict() directly within the mapper functions? As far as I know, we don't use snowflake IDs yet in Collectives, and I'd prefer to not add code handling this specific case before we introduce snowflake IDs.

[Koc]

$this->db->insertIgnoreConflict() works with plain tables/arrays of columns=>values. But I want to continue using entities like it was before. That's why I've introduced insertIgnoreConflict on a mapper level that accepts entity object and uses $this->db->insertIgnoreConflict() under the hood.