feat: interpretation panel

[crfmc]

Implements interpretation panel for demo's with the clinical information field

[sehilyi]

Should we respect the previous state of whether the clinical panel was opened? If I understand correctly, I think you are force-opening the clinical panel whenever the user selects a new demo. I think this could be disturbing to the user if they want the panel to be closed.

Suggested change

	setIsClinicalPanelOpen(!!demo?.clinicalInfo);
	setIsClinicalPanelOpen(!!demo?.clinicalInfo && isClinicalPanelOpen);

[sehilyi]

I assume this change was only for testing purposes?

Suggested change

	width: `calc(100% - ${0}px)`,
	width: '100%',

[sehilyi]

I think you could consider moving styles related to the clinical panel to a separate CSS file to prevent this file becoming longer, e.g., css/ClinicalPanel.css

[sehilyi]

Something to consider in the next round of update is further narrowing down the type definitions.

export type ClinicalInfo = {
    summary: SummaryItem[];
    variants: VariantItem[];
    signatures: SignatureItem[];
}

export type SummaryItem = {
    label: string;
    value: string;
}

export type VariantItem = {
    gene: string;
    type?: string; // if we know all the possible types, we can narrow down further, i.e., type: "Germline" | "homozygous loss" | ...;
    cDNA?: string;
    chr: string;
    start: string; // ideally this should be number
    end: string;  // ideally this should be number
    position: string;  // ideally this should be number
    handleClick?: () => void;
}

export type SignatureItem = {
    type: string;  // if we know all the possible types, we can narrow down further, i.e., type: "indels" | "point_mutations" | ...;
    count: string;  // this can be number
    label: string;
    hrDetect: boolean;
}