Length validation clean up

When using the REST API, I noticed that not all of the endpoint have the correct notEmpty + isXString validation combo, causing potentially unhelpful error messages. Therefore, I've gone ahead and did some clean-up in the lenght validation area:

- Make sure that both notEmpty and isXString are used where necessary
- Used test utility function to generate long strings