Section 2 | Coordinator: Coordinator Internal Notes Feature

### Dependencies
- Design is actively working on this feature, see: #736

#### Design
- #736

#### Engineering
- #677 created by Mira, engineering team to confirm if any work was done, since design is still finalizing notes.

### Context:

- This story covers a portion of functionality needed for #454

### The Problem

Coordinators currently have no structured method to capture valuable insights about Guests and Hosts that are not included in the pre-filled application. Coordinators require a structured way to log and access insights on Guests and Hosts to make more informed decisions and ensure consistency across the organization.

### User Story:

As a Coordinator, I want to write internal notes on Guests and Hosts to document insights, conversation history, and other important details not formally recorded in the HUU application. Notes will be shared across Coordinators within the same organization but remain hidden from applicants, ensuring better coordination, informed decision-making, and privacy.

### High Level Approach

The coordinator is able to add/edit/save/delete internal notes that are only visible to Coordinators.

### Acceptance criteria
- [x] When there is no note, The Coordinator assigned can add a note to any Guest/Host
- [x] If a note already exists any Coordinator can View the note
- [ ] If a note already exists the assigned Coordinator should be able to Edit the note
- [ ] Coordinator can Save their Edit of the note
- [ ] Prior to Saving, Coordinator can choose to cancel the Edit. The note should revert to it's prior state from the last time it was saved.
- [ ] Coordinator can easily add/view/edit note from the dashboard.
- [ ] Any Coordinator in the organization _can view_ existing notes
- [ ] _Assigned Coordinators_ can edit and save their own notes, maintaining an audit log of changes.
- [ ] A Coordinator can undo an edit before saving, reverting the note to its prior state

### Metrics
- Number of Guests/Hosts with notes vs total Number of Guests/Hosts
- Average number of characters in each Note.
- Number of times a Note is Saved (changed) per Guest/Host
- Frequency of note usage per coordinator
- Average time spent accessing or updating notes

### Considerations
- Coordinators will be using desktop or tablet--> use responsive design
- Notes should remain internal and not be visible to Guests or Hosts.
- Each Guest/Host should initially have only one note for MVP, but future iterations may allow multiple notes with categorization.
- Explore integrating search and filtering to enhance accessibility and usability.
- Track timestamps and Coordinator names to maintain continuity during personnel changes

### Future Considerations
- Allow for more than one note per Guest/Host