chore: pin COG to < 2

[joyceyan]

Reason for Change

updates all of the COG versions in data portal to <2, and specifies the schema version in the OntologyParser as 5.2.0. this means we'll fetch the latest version of COG that's compliant with 5.2.0.

when we bump the schema version in the future, we'll need to bump the version specified in OntologyParser. i've added this to step 10 in the confluence page

Testing steps

let's see what happens with the unit tests

Checklist 🛎️

• Add product, design, and eng as reviewers for rdev review
• For UI changes, add screenshots/videos, so the reviewers know what you expect them to see
• For UI changes, add e2e tests to prevent regressions
• For UI changes, verify impacted analytics events still work

not applicable here

Notes for Reviewer

[github-actions]

Deployment Summary

• backend_url: https://pr-7414-backend.rdev.single-cell.czi.technology
• backend_de_url: https://pr-7414-backend-de.rdev.single-cell.czi.technology
• backend_wmg_url: https://pr-7414-backend-wmg.rdev.single-cell.czi.technology
• frontend_url: https://pr-7414-frontend.rdev.single-cell.czi.technology
• delete_db_task_definition_arn: arn:aws:ecs:us-west-2:***:task-definition/dp-rdev-pr-7414-deletion:1
• migrate_db_task_definition_arn: arn:aws:ecs:us-west-2:***:task-definition/dp-rdev-pr-7414-migration:1

[nayib-jose-gloria]

looks like the ontologyparser is initiated in various spots w/o a version arg https://github.com/search?q=repo%3Achanzuckerberg%2Fsingle-cell-data-portal%20ontologyparser&type=code

this means they'll default to the latest schema version; in 1.3.1, that's 5.3.0 (which is not released yet). You should pass in 5.2.0 as an arg for all the OntologyParsers and then just shift all these to cellxgene-ontology-guide<2