Error Alignement with Commonalities

[bigludo7]

Problem description
Following Commonalities rules:

To be applied:
Error 429 must be added for location-retrieval (already present in location-verification & geofencing)
Errors 410 & 429 must be added to the callback endpoint in Geofencing
Error 409 must be added for POST /subscriptions in Geofencing

To be discussed:
Error code 500 & 503 could be removed but we need a decision for all 3 APIs for consistency
Error code 429 could be removed for GET & DELETE subscriptions in Geofencing

Expected behavior
Update yamls

Alternative solution

Additional context

[alpaycetin74]

Why would we remove 500 and 503 errors? There can be system level issues on the server side. Thank you.

[bigludo7]

Hi @alpaycetin74
See camaraproject/Commonalities#355 and discussion here: camaraproject/Commonalities#321 (comment)

[alpaycetin74]

I see, thank you @bigludo7

[jlurien]

We have to make some more alignments:

• Schema for errors must use the new template defining the allowed values as enum
• Adopt new errors for objects with device identiers