Create Uniprot -> Ensembl ID mapping file

[jaclynbeck-sage]

This PR addresses AG-1389 and creates a notebook in data_analysis/agora that:

1. Collects all Ensembl IDs used in ADT, except for druggability and what's in the gene_metadata file (because it includes druggability genes)
2. Queries UniProt for corresponding accession numbers
3. Saves the results in a 2-column table with columns UniProtKB_accession and RESOURCE_IDENTIFIER, as requested in the JIRA ticket.

The output file can be accessed here on Synapse.
The human-readable notebook can be found here on Github.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[beatrizsaldana]

Looks good to me! I also found that multiple uniprot ids map to a single ensembl id, and that not all ensembl ids have uniprot ids. I appreciated the sanity check!

[jaclynbeck-sage]

Looks good to me! I also found that multiple uniprot ids map to a single ensembl id, and that not all ensembl ids have uniprot ids. I appreciated the sanity check!

Yeah I think the multiple <-> multiple relationship should be ok, and at least mult. uniprot -> single Ensembl ID makes sense biologically. Not sure about mult. Ensembl ID -> single Uniprot but I think that has to do with how Ensembl labels things like pseudogenes and predicted genes so, it's probably all ok.

[JessterB]

lgtm!