[catalog-backend-module-okta]: provide a seam to exclude

[GoFightNguyen]

Context

Using the new backend system, I added the alpha export from @roadiehq/catalog-backend-module-okta v0.10.0`.
Everything works.

My issue occurs in how I handle acceptance tests. All the acceptance tests for my backstage implementation start their own instance of the backend. Each set of acceptance tests provide their own app-config.yaml in order to exclude the features not needed. For example, I have a custom catalog module that ingests data from RabbitMQ, in this case I do not want ingestion from Okta to occur. Thus, I would like a way to short-circuit the env.registerInit of oktaCatalogBackendModule

Possible Implementation

1. Provide a "null" implementation to provide for the entityFactory: EntityProviderFactory. Then a consumer of this module could conditionally use it.
2. Modify the oktaCatalogBackendModule to short circuit based on app-config.yaml missing catalog.providers.okta.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.