Announcement Issue F1

[srambhatla30]

Issue F1: fixtures/components for announcements

Developer Story:

• As an developer
• I have access to fixtures, components and storybook stories for a form and table for Announcements
• So that I can build future features for the Announcements table

Acceptance Criteria:

• [ ] There is a form component for announcements suitable for crud operations (similar to team03 form components, but with a nice large textarea for the announcement text.) Note that the commonsId is not part of the form; it will be set implicitly.
• [ ] There is a table component for announcements (similar to team03 table components) Note that the commonsId is not part of the table component; it will be the same for all entries in the table, so we will put it at the top of the page separately.
• [ ] There are fixtures that match the format of the GET operations for the API endpoints being worked on in the second issue. Note that the fixtures should be organized so that each set of announcements is for a single commons, since we only ever work with the announcements for one commons at at time, even though in the database they are all stored in the same database able.
• [ ] There are storybook entries for the form and table components. Note that the storybook entries for the table should focus on one commons at a time (see discussion above under fixtures).