Investigate running Keybase.io client in a container, as workaround for MacFuseSSHFS issue

After upgrade to macOS Ventura, the Keybase.io client pops up a warning that it cannot start the SSHFS subsystem. There is a known issue about it on the GitHub project, but it is actually an upstream problem, and may take some time to correct.

The impact is that the integrated KeybaseFS feature is not available on macOS, and so I can only browse these files in the webUI, or Linux/Windows machines, not on macOS with the CLI or Finder. As workaround, I have moved critical files to an alternate storage (MEGA.NZ - this is offline as well).

A similar problem with MacFuse happened in the upgrade from macOS Big Sur to Montery, and likely will happen again in the future. It would be interesting to see if the keybase.io container can be useful as a bridge to the filesystem.