Problem description
Found by @jlurien
400 OUT_OF_RANGE -> defined but not tested. I don't think we need it looking into the request body schema
400 LOCATION_RETRIEVAL.MAXAGE_INVALID_ARGUMENT -> Description seems similar to 422 UNABLE_TO_FULFILL_MAX_AGE. is it needed? We should remove it or clarify when to use it instead of the other

Expected behavior

• Remove 400 OUT_OF_RANGE as no UC for it.
• Remove 400 LOCATION_RETRIEVAL.MAXAGE_INVALID_ARGUMENT and keep only 422 UNABLE_TO_FULFILL_MAX_AGE

Alternative solution

Additional context