Qdrant settings for new cluster

[shanbady]

What are the relevant tickets?

Part of deploying https://github.com/mitodl/hq/issues/8910

Description (What does it do?)

This PR modifies QDRANT_API_KEY, QDRANT_HOST, QDRANT_SPARSE_MODEL and QDRANT_SPARSE_ENCODER so they get their values from the new _V2 environment variables which point to the new cluster.

How can this be tested?

1. checkout this branch
2. set QDRANT_HOST_V2 or QDRANT_API_KEY_V2 to some arbitrary value in your env and then validate that it shows up in settings.QDRANT_HOST or settings.QDRANT_API_KEY

Additional Context

The idea is that once the new cluster is populated with embeddings

1. we merge+deploy the qdrant-upgrade branch which will contain these V2 settings
2. follow up with ol-infra change to set the normal env vars to the new settings as well
3. remove _V2 settings and re-deploy

[github-actions]

OpenAPI Changes

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

2 changes: 0 error, 0 warning, 2 info
info	[new-optional-request-parameter] at head/openapi/specs/v0.yaml	
	in API GET /api/v0/vector_content_files_search/
		added the new optional 'query' request parameter 'hybrid_search'

info	[new-optional-request-parameter] at head/openapi/specs/v0.yaml	
	in API GET /api/v0/vector_learning_resources_search/
		added the new optional 'query' request parameter 'hybrid_search'

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