Cycle Analytics - Investigate gracefully handling 4xx errors

Problem

I noticed some 403 errors when testing !20192 (merged)

We should make sure we effectively handle 403, 401 and 422 (returns problems with custom stage form fields errors) to provide more useful feedback to the user.

Fields in the custom stage form will return a 422 error and details about the field(s) with errors

When a field error is returned from the server, we should:

• display an error message
• display the specific field error below the relevant field
• ensure the form can be resubmitted
• clear errors when the form is resubmitted