refactor: improve error handling for verification service

[bhavanakarwade]

• API routes should be self-explanatory & aligned with functionality.
• Change Promise<object> to an interface.
• Refactor responses (Only necessary fields should populate in response).
• Check status codes
• Check role-wise authentication to APIs with RoleGuards
• Check API status and statusCode should be checked properly.
• Error logs should be there wherever necessary.
• End-to-end testing.
• ESLint rules should not be disabled unless necessary
• Validation on Payload.

1. Apply trim() on payload.
2. Apply toString(), toNumber() datatypes properly to payloads.
3. Apply toOptional() if parameters are optionals.
4. Apply notNull for parameters of payloads if not optional.

• Error Response.

ex:

{
  "message": "User friendly message",
  "error": "Some error description/error stack",
  "statusCode": 400,
}

• API's :

• Get all proof presentations by OrgId

• Webhook call for store proof presentations

[bhavanakarwade]

completed