Passing invalid application_id format results in 500 error instead of 422 at /ui/login

[fisher60]

Summary

If an invalid application_id format is given, it results in a 500 internal server error i.e https://auth.abandontech.cloud/ui/login?application_id=fake&callback_uri=/ui

This should ideally raise a 422 Unprocessable Content (if the format is known to be invalid). We should perform some validation on the pydantic model to ensure the UUID is in the correct format. We must also ensure that even if the UUID is believed to be in the correct format, the only other error that can be raised here results in a 404 status. I.e if a bad UUID is passed to prisma, this should result in the application not being found, not a 500 server error.

The following URL correctly results in a 404 as it is a valid UUID format, but does not correspond to a real application: https://auth.abandontech.cloud/ui/login?application_id=cd022be1-35af-4248-8d70-4205ed1c20c7&callback_uri=/ui

[Lopkop]

#71