Managing GWAS Catalog study QC/flags

[DSuveges]

GWAS Catalog studies needs to be curated before ingestion because:

• Some studies are QTLs (p/q or metbolomics), that are not expected to be ingested at all.
• Some studies with summary statistics needs to be QC-d to make sure the ingested data meets requirements.
• If a study fails QC, it needs to be flagged and the results need to be propagated
• Only those studies should be clumped that have no QC flags.

This issue has synergies with #3101

[DSuveges]

Results of curation done for OT Genetics is expected to be hosted in our curation repo. There's a slight complication, that this file is expected to be regularly updated and the ETL run would depend on a main branch, ideally tagged version of the tracked curation file. It indicates that the release process needs to have two stages: upon ingestion phase, the QC flags are collected and the curation repo updated. in the ETL phase the upated curation file is used to get those list of studies which passed all qc (no qc flags).