Delete assigned resource must return HTTP status code 409 Conflict

[stiliyan-v]

Changes Made:

• Added the new exception class CompasAssignedLocationException for cases when a location with assigned resources is attempted to be deleted.
• Updated LocationsService.deleteLocation to throw CompasAssignedLocationException instead of the more generic CompasSclDataServiceException when deletion is not allowed.
• Introduced CompasAssignedLocationExceptionHandler to map CompasAssignedLocationException to a 409 Conflict HTTP response with a structured error body.

Testing Updates:

• Added a unit test for CompasAssignedLocationExceptionHandler to verify correct error response mapping.
• Updated service and resource tests to expect and use CompasAssignedLocationException instead of the previous exception.

[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

[david-monichi]

@clepski Hi, I just did a code cleanup and we would need your approval. Somehow this feels like a situation we mentioned last Retro where we should be able to merge ourself without your approval (just the code cleanup).

@Sander3003 Is it possible that at least I get the permission to merge for such cases?

[Sander3003]

Yes, let me check the permissions.

[Sander3003]

Bearingpoint has maintainer rights now.

[david-monichi]

Bearingpoint has maintainer rights now.

Thx, we will use them as we agreed on.

[david-monichi]

@Sander3003 I guess for development you would need to approve this PR:
#707