Add support to immunemarker data

[mauroz77]

Description

As a developer, I want the ETL to be able to process immunemarker data, which will have its entry in molecular_characterization table and will need the creation of a table in the database as well as transformation tasks in the ETL.

Acceptance Criteria

• [ ] Data is accessible using an endpoint

[mauroz77]

@mriios @Mandloi2309 the endpoint to access immunemarkers is ready in dev. Does it look ok?

Endpoint example: https://dev.cancermodels.org/api/immunemarker_data_extended?model_id=eq.TM01086

[
{
"model_id": "TM01086",
"data_source": "JAX",
"source": "xenograft",
"sample_id": "TM01086F269P0",
"marker_name": "MSI",
"marker_value": "MSI-S",
"essential_or_additional_details": null
},
{
"model_id": "TM01086",
"data_source": "JAX",
"source": "xenograft",
"sample_id": "TM01086F269P0",
"marker_name": "TMB",
"marker_value": "3.23",
"essential_or_additional_details": "0.0-304.42 (across all JAX PDX models; TMB > 22 is considered high)"
}
]

[Mandloi2309]

Looks good to me!

[mauroz77]

@mriios the Immunemarkers filter is visible now (dev). We just need that the UI uses it with the cs operator instead of in. For instance, https://dev.cancermodels.org/api/search_index?immunemarkers_names=cs.{%22HLA-A%22}&limit=10 instead of https://dev.cancermodels.org/api/search_index?immunemarkers_names=in.(%22HLA-A%22)&limit=10

Private Zenhub Image