avalanche_binary: ~/go/src/github.com/ava-labs/avalanchego/build/avalanchego
repo_folder: ~/go/src/github.com/ava-labs/avalanchego
repo_name: ava-labs/avalanchego
repo_url: https://github.com/{{ repo_name }}
repo_branch: dev

avalanche_binary: "{{ repo_folder }}/build/avalanchego"
repo_folder: "~{{ ansible_user }}/go/src/github.com/ava-labs/avalanchego"
repo_name: ava-labs/avalanchego
repo_url: https://github.com/{{ repo_name }}
repo_branch: dev

Fix installation when build user != installation user
ansible: Fix installation when build user != installation user

When the ssh user (e.g. pi) did not equal the superuser (e.g. root),
then the ava-install role could not find the binary that had been built.

Using `~{{ ansible_user }}` ensures the path expands to the same
location, regardless of whether privileges have been elevated with
`become: true`.

When these roles were first developed and tested on a DO Droplet the
build user and install user were both root. This meant build and install
happened as the same user.
