Add display of annotations to Markers component (UI)

[elynema]

Description

For AVAnnotation grant effort, Ramp needs to be able to display annotations more generically. The Markers component can be re-used for this purpose. The name of the component can be set through a prop.

Questions

• How to handle multiple annotation bodies? Do they all get concatenated into a single annotation? Do we want all textualbodies regardless of purpose or just some?
• When providing a label to filter annotation sets and to display next to each annotation, do we use the AnnotationPage label (Aviary and AvAnnotate provide) or the textualBody with purpose=tagging label?
• Annotations with motivation of commenting (AVAnnotate) and supplementing (Aviary) were called out. Are there other motivation types that we need to support?

Done Looks Like

• Extend Markers display component

• Provide a multi-select filter drop-down at the top allowing users to select one or more annotation sets to display. When not expanded, the drop-down should say how many sets are selected.

• Display annotations with motivation commenting (AVAnnotate) or supplementing (Aviary)

• For a given annotation body, the label/value pair displays, ex: "Title: Bladderball"

• If there are multiple annotation bodies, all should be displayed

• If there is an annotation body with purpose=tagging, that value should be displayed as the label for the annotation

• Props exist for: tab label, whether or not the tab scrolls, which motivation annotations should be displayed

• Time should be displayed as either a single time (if the annotation reference a timepoint or a range if referenced in annotation). If a range, the entire range should link to the starting timepoint in the range.

• Do not display markers on the time rail for first iteration

• If not displaying highlighting annotations (markers), then annotations should display with timepoint/range and label(s) on the first line, with annotation text below and likely to be muti-line. If the annotation text is >6 lines, implement some kind of expand to show the entire annotation text, which could be very long