Better way to clone in an existing home directory.

Not sure what the deal is here (IIRC I copied this config for colors
from somewhere). I'll deal with it some other time.

- Set filetype to unix by default.
- Use the filetype plugin to have per-filetype configuration.
- Use 2 spaces for YAML and Terraform files.
- Move Python configuration from .vimrc to filetype plugin.

Whem the database for clipped gets corrupted, it needs to be deleted and
the application restarted. Script that.

- More scripty (set -eu, not just an alias in a script).
- Update appstream data.

This reverts commit 393f2782.

If I want that behavior I would be explicit about it and use the `unssh`
alias instead.

It's breaks a few things.

By default just show what will be done with the git clean aliases.
Require passing -f to actually delete the files.

Git script to remove temp work tress and prune work trees.

So there's a different default private key and also separate the public
keys I use to encrypt for other people in Endless.

Use the variable file matching the workspace when validating. Also when
validating and formatting, show the diff.

The prune_ssh_sockets shell function would always delete the
ControlMaster sockets (the open file handlers would have a random suffix
and the check would always show that the socket wasn't open by any
process). Instead add a prefix to the ControlMaster sockets and ignore
them when pruning. Those sockets are always deleted when the process
exists. Also, mark the vim filetype for the ssh config fragments as
sshconfig.

Use the openvpn endpoint as a jump host, it eases the firewall
restrictions. Clean up duplications.

They have hashes but aren't secrets.

Don't delete sockets that are still in use (have an open ssh client
listening).

So now I can run `$(eval docker remote hostname)`.

- Add toolbox script, bash completion.
- Better ansible-local in Makefile (match shell alias).
- Delete gcloud SDK bash completion, the mirror in github is gone.
- Update to newer version of binaries and vendored files.

Per
https://docs.ansible.com/ansible/latest/reference_appendices/config.html#the-configuration-file
the ~/.ansible.cfg file is ignored if another is found first. So use
environment variables instead so they work with all of my setups (the
internded purpose). Also, for the ansible-local and
ansible-local-playbook aliases, use the Python3 interpreter that was
used to run Ansible in the first so that modules (like postgresql_privs)
that require Python module have access to them.