feat: add "Setup auth org ID" action for Enterprise Customers

[pwnage101]

ENT-8169

screenshots

Button NOT present when the ENTERPRISE_SSO_ORCHESTRATOR_CONFIGURE_EDX_OAUTH_PATH setting is NOT defined:

Button present when the ENTERPRISE_SSO_ORCHESTRATOR_CONFIGURE_EDX_OAUTH_PATH setting is defined:

Clicking the button leads you to a confirmation page with help text:

Clicking "Setup auth_org_id" results in a success message displayed:

Finally, clicking "Cancel" navigates back to the "Change Enterprise Customer" screen with updated value for the "Auth org id" field.

Merge checklist:

• Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • base.in if needed in production but edx-platform doesn't install it
  • test-master.in if edx-platform pins it, with a matching version
  • make upgrade && make requirements have been run to regenerate requirements
• make static has been run to update webpack bundling if any static content was updated
• ./manage.py makemigrations has been run
  • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.
  • This should be run from either a venv with all the lms/edx-enterprise requirements installed or if you checked out edx-enterprise into the src directory used by lms, you can run this command through an lms shell.
    • It would be ./manage.py lms makemigrations in the shell.
• Version bumped
• Changelog record added
• Translations updated (see docs/internationalization.rst but also this isn't blocking for merge atm)

Post merge:

• Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
    (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• PR created in edx-platform to upgrade dependencies (including edx-enterprise)
  • This must be done after the version is visible in PyPi as make upgrade in edx-platform will look for the latest version in PyPi.
  • Note: the edx-enterprise constraint in edx-platform must also be bumped to the latest version in PyPi.

[pwnage101]

I don't know where to put this translation, do I need to run a make command or something?

[iloveagent57]

You can run make extract_translations I think? https://github.com/openedx/edx-platform/blob/2209549e68776f5db3c77a571bba115918fcf3f7/Makefile#L40-L53
That said, you're making changes to an internal tool, so I wouldn't let this be a blocker.

[pwnage101]

• Updated text to just match what Joe proposed, with minor alterations.
• Updated the text "Auth org id" to be consistent across all user-facing text, and matches the pre-existing field display name.
• Added test coverage and PR screenshots for success message display.