local-app: Handle access token storage if keyring isn't running on enviroments such as WSL

[ajhalili2006]

Is your feature request related to a problem? Please describe

One of the painpoints of running the Local Companion in server environments where there's no GUI installed by default or in case of WSL, the distro's init system of choice isn't ran as PID 1 so we need to use the good old /etc/init.d scripts.

mikedmoy@HaliliFam-Win10-Dell: ~/git-projects/oss/gitpodified-workspace-images recaptime-dev-mainline!
$ gp-localapp                                                                                            [19:44:41]
INFO[0000] writing workspace ssh_config file             ssh_config=/tmp/gitpod_ssh_config
2022/02/13 19:44:50 failed to unlock correct collection '/org/freedesktop/secrets/aliases/default'
FAIL

Describe the behaviour you'd like

Possibly store the access token generated from the OAuth authorization code exchange as an SQLite database or YAML config in ~/.config/gitpod-local-companion (~/AppData/Local/gitpod-local-companion in Windows).

Describe alternatives you've considered

While --mock-keyring flag might be closest alternative to this situation, we need to literally reauthenicate every time we fire up the Local Companion binary.

Additional context

No response

[loujaybee]

Thanks for raising, @ajhalili2006. Since local companion app is still beta, we'll be taking a look into this as part of the move of local companion to GA. Thanks! 🙏

Also related roadmap item: #7185

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.