Bug: Edge Models - Module validation returns a HTTP 422 error

[kbeaugrand]

Expected Behavior

Validation issues should be displayed to the user.
The error should be handled by HTTP 400 instead.

Required fields should be also required on the UI !

Current Behavior

An error 422 is catched by the browser but not displayed...

Steps to Reproduce

1. Create a new Edge model
2. Add a new module
3. Do not edit the module

Context (Environment)

Portal version:
LoRaWAN Stack version:

Logs

Additional Information