Add EDI authentication authorization in legionctl

[kirillmakhonin]

We need to protect EDI server with dex.
Also we need to add auth functionality to legionctl tool.
Question to discuss: which credentials should be passed to legionctl tool, dex token or plain login and password (legionctl sends it via HTTPS)

Login from local dev should result profile with all required endpoint and credential.

[kirillmakhonin]

As a variant, next flow is possible:

1. New entity named auth tool has to be added.
2. auth tool has to operate with DEX directly (not in proxy gate mode)
3. EDI has to be closed by DEX (in proxy gate mode)
4. On each remote command legionctl tool can get 401/403 HTTP code in response.
5. In cases of 401/403 code legionctl has to request auth tool with required scope (e.g. enclave and functions). On response auth tool generates web URL (that is handled by auth) closed by dex.
6. Client receives this URL in console and, if it is possible, browser opens with URL
7. Client has to be redirected from URL to DEX (standard way), then redirected back with oauth2 token
8. auth web view has to display token and try to connect to listened by legionctl local port using standard XHR web request to provide token automatically.