fix: wrap backend errors in json messages

[halfwhole]

Problem

The frontend is unable to parse backend error messages correctly if they do not come in the standard JSON message format, i.e. { message: "..." }

Solution

Use jsonMessage() on error messages returned in the backend to wrap it in a JSON message.

• This is consistent with other instances of res.[badRequest/notFound/serverError](...) in the backend codebase, which all use jsonMessage() as well.

[jimvae]

nit: was trying to simulate the errors and just wanted to confirm that this is the intended behaviour if we call this api without limit

Screen.Recording.2022-09-29.at.12.06.10.AM.mov

This is because under the UserController,extractUrlQueryConditions changes the limit to 1000 as the default

[halfwhole]

from git blame, I see that the limit of 1000 has been there for a while now (last modified 2 years ago in this diff) - seems like the intended default behaviour to me!

[jimvae]

from git blame, I see that the limit of 1000 has been there for a while now (last modified 2 years ago in this diff) - seems like the intended default behaviour to me!

Alright! other than that LGTM!