Upgrade Catalog to use CKAN 2.10.5

[FuhuXia]

User Story

Upgrade Catalog to use CKAN 2.10.5

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• [x] Catalog CKAN status shows ckan_version: "2.10.5"
• [x] Finished harvest jobs.
• [x] QA done, focusing on changes from the changelog.
• [x] Catalog requirement.in file is updated with ckan upstream.

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[rshewitt]

All of these are introduced by ckan 2.10.4 and should be resolved by upgrading to 2.10.5

• Server-Side Request Forgery (SSRF) (new) [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-CKAN-7786366]
• Information Exposure Through an Error Message (new) [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-CKAN-7786369]
• Cross-site Scripting (XSS) (new) [High Severity][https://security.snyk.io/vuln/SNYK-PYTHON-CKAN-7786367]

[FuhuXia]

CKAN core 2.10.5 is deployed to catalog and catalog-next. https://catalog.data.gov/api/action/status_show https://catalog-next-dev-datagov.app.cloud.gov/api/action/status_show