Migrations Fail to Find Goose

[srwadleigh]

When running a migration target against an external database, without using containers, the migrations fail looking for the goose binary. For example running make migrate_pre_batch_set by hand from this repo.

The make script is looking for goose at /bin/goose but because goose is installed with go get as part of the migration process itself on a live system goose ends up in the respective user's go path ~/go/bin/goose

Ideally we would defer to the local $PATH to handle the location the binary