Investigate & document improvements to process of initial configuration of GitHub OAuth

[aaronkanzer]

There are a handful of manual steps required to properly configure the OAuth flow to successfully work for the LINC (and Dandi) Archive projects.

The process initially stems from a custom migration within the api Django app: https://github.com/lincbrain/linc-archive/blob/master/dandiapi/api/migrations/0003_default_oauth_application.py#L6

Follow-up steps include going into the Django Admin panel to manually connect the Client ID and Secret from the GitHub OAuth app.

The purpose of this ticket is to find and implement ways of making this more straightforward, or at the very least, document this process for others to follow.

Relates to https://github.com/orgs/lincbrain/projects/2?pane=issue&itemId=47716813

Cc @kabilar -- just tagging you here with regards to follow-up meetings with Roni / Kitware. Let me know if I can provide further context.

[kabilar]

Hi @aaronkanzer, has this process been added to dandi/handbook#104?

[aaronkanzer]

@kabilar -- yes there is documentation for the initial configuration in dandi/handbook#104

Not sure whether or not we would want to keep this Issue open though, as I still think there is area for improvement for what I have in the handbook now -- perhaps I'll wait to see how the Ember team fairs with the docs here<>when they set up auth, and update appropriately