Testing Inventory for CKAN 2.9 under Py3

[mogul]

User Story

In order to increase confidence that we are ready to run in a Python 3 environment, the team wants to validate our applications with all their extensions under Py3.

Acceptance Criteria

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

• GIVEN all relevant ckan extension is upgraded to CKAN 2.9 + PY3
  When the testing environment for inventory-app supports CKAN 2.9 + PY3
  THEN the inventory-app tests can run and pass \

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]
Since they're not all consistent, we want to make sure we're using all the right branches/versions of the various extensions in inventory and catalog, and ensure they're all at least minimally working correctly in an integrated deployment.

Security Considerations (required)

None.

Sketch

Any necessary changes go on main (we have no expectation to backport to CKAN 2.8/Py2)

• Use the cloud.gov-provided Python buildpack (which is Py3)
• If we need an integration test to validate each extension is working correctly, we add it
• The local test environment is updated to use the openknowledge foundation ckan-dev image

[jbrown-xentity]

Inventory is complete (deployment run).

Catalog will be tackled in a separate ticket.