WebUI cannot access authenticated bacalhau node about bacalhau

[frrist]

Additionally we will need a way to modify the port the WebUI uses to access bacalhau. Since when bacalhau is run with TLS enabled the RPC is served on port 443 rather than the insecure default of 1234

[simonwo]

Notes on what needs to be done are here: https://docs.bacalhau.org/dev/auth_flow#authnz-in-the-web-ui

The Web UI currently does not have any authn/z capability, and so can only work with the default Bacalhau configuration which does not limit unauthenticated users from querying read-only API endpoints.

To upgrade the Web UI to work in authenticated cases, it will be necessary to implement the algorithms noted above. In short:

1. The Web UI will need to query the auth API endpoint for available authn methods.
2. It should then pick an appropriate authn method, either by asking the user, choosing based on known available data (e.g. existing presence of a private key), or by picking the only available option.
3. It should then run the authn flow for that type:
   • For challenge types, it will need a private key. It should probably generate and store one persistently rather than asking the user to upload theirs.
   • For ask types, it will need to parse the input JSON Schema and present a web form to collect the necessary authn credentials.
4. Once it has successfully authenticated, it should persistently store the access token and add it to all subsequent API requests.