feat(core): add guardrails to update template endpoint

[evebrnd]

PR Description

What this PR Provides

Enforce the following business rules:

• All PropertyDefinition names within a single template must be unique
• All RelationDefinition names within a single template must be unique
• The targetTemplateIdentifier of a RelationDefinition must reference an existing EntityTemplate
• All type changes of PropertyDefinition are blocked. Once a property is created, the type cannot be changed

Review

The reviewer must double-check these points:

• The reviewer has tested the feature
• The reviewer has reviewed the implementation of the feature
• The documentation has been updated
• The feature implementation respects the Technical Doc / ADR previously produced

How to test

Happy Path

• Removing a property or renaming it (delete and create) must return a 200 OK. The system must purge associated property values in the database for existing entities (no orphan data).
• Database integrity - Upon a successful remove operation, a GET on the entity property/relation tables must not return any rows for the old identifiers

Error Path

• Duplicate properties: A PUT request with two properties with the same name must return 400 Bad Request.
• Wrong Relations: If targetTemplateIdentifier references a template that does not exist in the entity_templates table, the request must return 400 Bad Request.
• Type change: If the type of a property is changed, PUT request must return 400 Bad Request.

Breaking changes

N/A

[sonarqubecloud]

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