Publish pre-flight: field/component errors match spec

### As an author I want field errors to easily stick out on a page and give me specific information about the error so I can resolve it.
#### Describe the solution you'd like:
- [ ] Component-level error messaging
- [ ] Design: Style matches mocks
- [ ] Content: [use this copy](https://github.com/cityofaustin/techstack/issues/3926#issuecomment-588425223)
#### Acceptance Criteria
- [ ] The styling of the error messages matches the mocks (icon is offset from fields, text is correct size, color, in the right place)
- [ ] The content of each error matches the provided list
#### Outstanding issues:
I'm not sure that the specific icon used by design is added to joplin yet. Is the 'warning' icon good enough for now? (seen here: https://joplin-staging.herokuapp.com/admin/styleguide/ )

Otherwise we can see if the icon is part of material icons and whether or not it can be used in the template as pictured.

Review the linked content list in issue 3926 and the Joplin staging styleguide before locating the field/component error templates and styles. Compare the current warning icon and error presentation with the referenced mocks; done means the specified copy, icon treatment, placement, size, and color match the acceptance criteria.

Written by the indexing model from the issue text.