Task Description (Required)

<Task description>

In RHDH v1.3 and higher versions, by default it is expected that users be added to the catalog. In their release notes it outlines the steps you need to take to add users from an organization. As of right now it looks like it is only for GitHub. Additionally, you can avoid this need to add users to the catalog by setting 'dangerouslySignInWithoutUserInCatalog' to true. We should add this as something you can opt-in for using the configuration scripts, and properly document its use in the documentation.

You can find the release notes about this change here: https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/release_notes/breaking-changes#removed-functionality-rhidp-3048

Documentation on setting this up can be found here: https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/authentication/index#enabling-authentication-with-github

In order for this issue to be marked as complete the following should be accomplished:

• Script updated to set the authentication with GitHub orgs
• Documentation updated for all use cases (installer script + manual, pre-existing script + manual)
• The dangerous sign in (non-prod use) is also documented and added as an option

If this requires Change Management, complete sections below: 

Change Request 

<Select which item is being changed>

[ ]  Add New Tokens

[ ]  Rotate Tokens

[ ]  Remove Tokens

[ ] Others: (specify)

  Environment

<Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

[ ]  Stage OR

[ ]  Prod

  Backout Plan

<State what steps are needed to roll back in case something goes wrong>

  Downtime

<Is there any downtime for these changes?  If so, for how long>

  Risk Level

<How risky is this change?>

  Testing

<How are changes verified?>

  Communication

<How are service owners or consumers notified of these changes?>