Support building as user without sudo rights

[pbrkr]

The eosio build process should be self-contained and not require sudo to litter the /usr/local directory. This will allow eosio to be built on one machine, packaged and then deployed cleanly to many machines. It will also allow us to follow best practice and build as a non-root user who does not have sudo permissions.

[jgiszczak]

EOS.IO requires a large number of dependencies, some of which are not available as operating system packages. /usr/local was created for the express purpose of hosting locally built libraries and programs. For those who don't which to use the native filesystem, Docker is supported. Linux also runs well in VMs. Other container solutions are not directly supported, but are expected to work. Our supported operating systems provide many build environment alternatives, and users and admins are expected to use their discretion to pick the solution that best meets their needs.

[pbrkr]

What is the supported process for building eosio on one machine, packaging and then deploying to other machines? The docker build is currently broken (See #4714 & #4552) and has discrepancies in what is built (See #4734).