feat(DATAGO-119348): Project Sharing POC

[rudraneel-chakraborty]

What is the purpose of this change?

This is a POC code for the project sharing feature. Will be used for KA and collaborations with UX and PM

How was this change implemented?

Added project sharing APIs with role-based access control:

• Fixed ProjectRepository.update() to allow editors
• Added 5 service methods (share, get/update/remove collaborators, role check)
• Added 4 REST endpoints (POST /share, GET /collaborators, PUT/DELETE /collaborators/{id})
• Added DTOs for sharing requests/responses
• Two-layer permissions: RBAC scopes (project:share) + database roles (owner/editor/viewer)

Key Design Decisions (optional - delete if not applicable)

This is POC. KA will further polish the design

How was this change tested?

• Manual testing: [describe scenarios]
• Unit tests: [new/modified tests]
• Integration tests: [if applicable]
• Known limitations: [what wasn't tested]

Is there anything the reviewers should focus on/be aware of?

Special attention areas, potential risks, or open questions

[sonarqube-solacecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 70%)
B Security Rating on New Code (required ≥ A)

See analysis details on SonarQube

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