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