Implement error pages

[elliottSlee]

User Story

As an applicant I want error pages that inform me of what went wrong and what I can do so that I can resolve any issues I encounters.

(Copy paste code from CIIP/CIF and release npm package)

Description

Suggestions from CAS: https://happo.io/a/336/components?projectId=1010&target=chrome&component=500%20page%20server-side&variant=default

Wireframes

Acceptance Criteria

• [ ] ErrorContext
• [ ] 404
• [x] 500

#

# #

[wenzowski]

Presumably we want to have an ErrorContext https://github.com/bcgov/cas-cif/blob/develop/app/contexts/ErrorContext.ts

…installed in our app page… https://github.com/bcgov/cas-cif/blob/develop/app/pages/_app.tsx

With 404 page example https://github.com/bcgov/cas-cif/blob/develop/app/pages/404.tsx

And 500 page example https://github.com/bcgov/cas-cif/blob/develop/app/pages/500.tsx

[matthieu-foucault]

The ErrorContext's purpose is to have an application-wide method to display errors (e.g. "Your application could not be submitted"). 404 and 500 pages should be the only ones that are implemented, not the list of error pages that are currently in the acceptance criteria.

The 404 error message should be tweaked: The responses may not have been saved (and that message may not make sense to the user), and they may not need to log in again, or be logged in in the first place

[matthieu-foucault]

Please add your planning poker estimate with Zenhub @VB-at-Bis

[matthieu-foucault]

Not sure the ErrorContext should be part of the AC...