Designate DNS – “not clear message” while trying to set quotas using some non existing quota type

[Arkady Shtempler]

### Scenario ###
Try to set quotas using not existing quota type in its body.
Patch to reproduce: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/839499

### Expected result ###
quota_resource_unknown type error with a clear error message

### Actual result ###
2022-04-27 18:32:22.620 521817 INFO tempest.lib.common.rest_client [req-3e2410a7-e057-4f60-99a6- https://192.168.122.68/dns/v2/ 0.166s
2022-04-27 18:32:22.620 521817 DEBUG tempest.lib.common.rest_client [req-3e2410a7-e057-4f60-99a6-
        Body: {"zones": 380162, "zone_records": 292536, "zone_recordsets": 552377, "recordset_records": 337400, "api_export_size": 855422, "tempest-819388308": 777}
    Response - Headers: {'date': 'Wed, 27 Apr 2022 18:32:22 GMT', 'server': 'Apache/2.4.41 (Ubuntu)', 'content-type': 'application/json', 'content-length': '152', 'x-openstack-request-id': 'req-3e2410a7-e057-4f60-99a6-https://192.168.122.68/dns/'}
        Body: b'{"code": 500, "type": "quota_resource_unknown", "message": "%s is not a valid quota resource", "request_id": "req-3e2410a7-e057-4f60-99a6-

The actual error message is “%s is not a valid quota resource” and it probably had to be something like: “tempest-819388308 is not a valid quota resource.”