SPIKE: Moving target dependencies between dev/release/main API and OIDC branches

[lbeaufort]

We need to be able to redeploy to the production space. If we make changes to the main branch of the mozilla package (like this: fecgov/mozilla-django-oidc@bd411b4) the API main branch will be behind and will cause builds to fail until it catches up. Example: https://app.circleci.com/pipelines/github/fecgov/fecfile-web-api/3497/workflows/5de88b39-7a68-4640-af9c-302cf7a0571b/jobs/10942

We need to be able to check dependencies on both project, with some flexibility on backwards compatibility. We might need to manage releases for mozilla package.

Business Reason

As a developer, I will be able to redeploy to the production environment so that I can fix problems quickly

Acceptance Criteria

If [precedent]
When [action]
Then [result]

QA Notes

null

DEV Notes

null

Design

null

[exalate-issue-sync]

Aurelia Khorsand commented: Duplicate of FECFILE-1396 (#892)