Support tracking libraryType in MHC results and ETLs

[bbimber]

@brentlogan: these changes are an extension to the MHC typing storage and ETLs. They mostly impact the PRIMe-seq side, but will ultimately need to be deployed to PRIMe.

Can you confirm what LK version PRIMe is running? I would like to deploy the PRIMe-seq parts of this first, stage data, and then add the PRIMe pieces. Because I think you update less frequently, this might just happen naturally.

[brentlogan]

@bbimber PRIMe is currently running on LabKey 26.3. We're planning to upgrade to LabKey 26.7 in the first half of November (and do the PostgreSQL migration sometime late Q1'27).

[bbimber]

@bbimber PRIMe is currently running on LabKey 26.3. We're planning to upgrade to LabKey 26.7 in the first half of November (and do the PostgreSQL migration sometime late Q1'27).

OK, perfect. This PR is mostly aimed at tracking additional detail on the raw MHC data. That field will be ETL'd to PRIMe, but it isnt really needed, nor will it be visible to normal users.

[bbimber]

Hi @brentlogan: sorry if my last post wasnt clear. Since prime is on 26.3 and this is targeted 26.7, there is no possibility you will deploy it until PRIMe-seq is staged (although it wouldnt harm anything if it was). It looks like tests passed - do you need anything else to approve this?