update wis2box-auth to utilize Keycloak

[tomkralidis]

The current wis2box authentication and authorization workflow uses wis2box-auth to manage and authorize dataset access if specified by the wis2box administrator. wis2box command-line utilities provide token management interfacing with wis2box-auth. API and UI requests on authorized data are sub-requested in nginx against wis2box-auth.

Driven by #479, we decide to add a Keycloak for enhanced authentication workflow/options, and update of wis2box-auth to interface with keycloak for authorization management. API and UI users would, then, enter username/password information, which would result in a cookie utiliized as part of the browser session (in addition to direct API access/workflow via CLI or JavaScript, for example).

[tomkralidis]

Consideration for a workaround: update wis2box-auth to lock down /processes/PROCESS_ID/execution to require token/auth workflow.

[tomkralidis]

Bump to next sprint for review/discussion of @isedwards' PR.

[tomkralidis]

@tomkralidis to setup catch-up discussion for @isedwards on past / future PR

[tomkralidis]

2024-01-17:

• need to resolve issues w/ hostname address
• use envsubst in entrypoint.sh to substitute accordingly
• should have an update this week

[tomkralidis]

2024-02-06: @maaikelimper to help on completing integration with the rest of the wis2box stack.

[tomkralidis]

2024-02-13: @maaikelimper to continue following priority integrations in this sprint.