Design Wiki: Feedback and Updates

### Overview
We need a wiki to explain the protocols for what designers should do when receiving feedback or updates on their issues.

### Details
- During a review in a meeting, take notes. Paste the notes in a comment. If you are not present for the review, the lead will paste notes in a comment.
- Update the issue accordingly.
- Move the issue to the appropriate GitHub board column.
- [Bus factor](https://en.wikipedia.org/wiki/Bus_factor): GitHub issue updates and Figma files should be organized such that anyone else who comes onto the issue should be able to look at it, know what's going on, and then continue working on it.
- Comments that have been addressed should be hidden as resolved. Examples:
- Feedback that has been addressed
- Updates that have been incorporated into the issue description, if necessary
- Questions that have been answered
- Answers that have been incorporated into the issue description, if necessary

### Action Items
- [ ] Create a page for Feedback and Updates in the wiki.
- [ ] Add a link to the created wiki page in the Resources section below.
- [ ] Write documentation for the wiki.

### Resources
- [Design wiki](https://github.com/hackforla/tdm-calculator/wiki/Design)

Start with the linked Design wiki page and review its structure and Resources section. Create a Feedback and Updates page covering the listed review, issue-update, board-column, bus-factor, and resolved-comment practices, then add its link to Resources and confirm all action items are complete.

Written by the indexing model from the issue text.