Add Okta support to generate endpoint

[earmenda]

Closes #810

Code Changes

• Add okta-systems option to generate endpoint
• Refactor okta generate code paths to be called from cli and api
• Update usages of organization key to use common option organization_fides_key_option
• Update generate integration tests to also call okta code path

Steps to Confirm

• Automated tests

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation Updated:
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md

Description Of Changes

• Straight forward change other than dealing with some async weirdness. Old code path used asyncio.run which cant be called from the api path.

[SteveDMurphy]

Looks good to me @earmenda 👍🏽

If you think it makes sense to do, the only suggestion/nit I might have is that I get a little twisted with some of the function names in system.py (e.g. generate_system_okta, generate_okta_systems)

[ThomasLaPiana]

A few nits but otherwise LGTM!

[earmenda]

Looks good to me @earmenda 👍🏽

If you think it makes sense to do,
the only suggestion/nit I might have is that I get a little twisted with some of the function names in system.py (e.g. generate_system_okta, generate_okta_systems)

@SteveDMurphy I agree it is a little bit odd but I'd say it is only because the system.py functions need to have the cli functions taken out. Right now the function generate_system_okta maps to the cli command generate system okta but it probably doesn't belong there. There is also a generate_okta_systems function which DOES belong here and does exactly what it says.