SPIKE: Define what frontend needs from backend for NOTES

1. Review all frontend user stories for notes
2. Create user stories in MODNOTES for what is expected from the backend

NOTES mockups: https://drive.google.com/drive/folders/1WszhQDUmN7bO2kPJVu4nNEuAtymMNICw

SPIKE RESULTS:
------------------------
1) Notes ui stories review:

1. duplicate plugin stories:
Plugin for search and attach notes: https://issues.folio.org/browse/UINOTES-1
Assign a note | Display a Notes pop-up: https://issues.folio.org/browse/UINOTES-12
Common notes accordion: https://issues.folio.org/browse/UINOTES-3

2. https://issues.folio.org/browse/UINOTES-10
q: Should we move unassign to the accordion?
Doing so we we are able to create Notes app more universal app that could be used in different apps
3. https://issues.folio.org/browse/UINOTES-8
Need to be updated with the scenarios on what should be when we click cancel button
1. duplicate stories
1. https://issues.folio.org/browse/UINOTES-9
2. https://issues.folio.org/browse/UINOTES-6
--------------------------
2) Notes backend stories created:

https://issues.folio.org/browse/MODNOTES-64
https://issues.folio.org/browse/MODNOTES-65
https://issues.folio.org/browse/MODNOTES-66
https://issues.folio.org/browse/MODNOTES-67
https://issues.folio.org/browse/MODNOTES-68