Add Canvas platform for learning resources

[mbertrand]

What are the relevant tickets?

Related to https://github.com/mitodl/hq/issues/7779

Description (What does it do?)

• Adds a new LearningResourcePlatform entry for canvas
• Assigns that platform to resources upserted by the canvas ETL pipeline

How can this be tested?

• If you haven't done so already, run ./manage.py backpopulate_canvas_courses on the main branch.
• Switch to this branch.
• Run ./manage.py backpopulate_canvas_courses --overwrite on this branch.
• Check that the ingested canvas courses now have platform=canvas: http://ai.open.odl.local:8065/admin/learning_resources/learningresource/?etl_source=canvas
• Check that there are contentfiles where platform=canvas: http://ai.open.odl.local:8065/api/v1/content_file_search/?platform=canvas
• Time permitting, you can also run ./manage.py generate_embeddings --all --overwrite and then check http://ai.open.odl.local:8065/api/v0/vector_content_files_search/?platform=canvas to make sure some files are returned

[github-actions]

OpenAPI Changes

Show/hide 3 changes: 0 error, 0 warning, 3 info

3 changes: 0 error, 0 warning, 3 info
info	[request-property-enum-value-added] at head/openapi/specs/v1.yaml	
	in API POST /api/v1/learning_resources_user_subscription/subscribe/
		added the new 'canvas' enum value to the request property 'platform/items/'

info	[request-property-enum-value-added] at head/openapi/specs/v1.yaml	
	in API POST /api/v1/learning_resources_user_subscription/subscribe/
		added the new 'canvas' enum value to the request property 'platform/items/'

info	[request-property-enum-value-added] at head/openapi/specs/v1.yaml	
	in API POST /api/v1/learning_resources_user_subscription/subscribe/
		added the new 'canvas' enum value to the request property 'platform/items/'

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[shanbady]

In heroku we had a release-phase script that ran the data migrations and a few other things. Not sure if this has carried over to EKS but we should make sure its there otherwise this wont get applied on deploy

[shanbady]

changes look good. deploying this will be a good test to see if the heroku deploy scripts in k8 works