Feature/problemdetails

[wotwot563]

Description

This issue makes our errors conform RFC 7807, with added GUIDS for easy error traceback.

Type of change

• New feature (non-breaking change which adds functionality)

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.
These steps will be used during release testing.

1. make a request that is not valid:
   example: do a get request to /api/Project/-1
2. the result should be:
   header:
   Content-type: application/problem+json
   body:
   {
   "title": "Failed getting project.",
   "status": 400,
   "detail": "The Id is smaller then 0 and therefore it could never be a valid project id.",
   "instance": "D590A4FE-FDBA-4AE5-B184-BC7395C45D4E"
   }

Link to issue

Closes: #80

[Brend-Smits]

Why are postman tests in this branch as well?

[Brend-Smits]

Next time please keep the checklist in the pull request in the description, just check what you have done :)
Can you assign it to the correct project board?

[StijnGroenen]

Have you added an explanation or guide to the wiki so developers know how they must write error responses? If not, please add it.