Resilient build and installation

[JimLarson]

During the emerynet deployment of mainnet1B-rc0, many validators built as instructed but then copied the agd Go binary to another location. Some copied the adg shell script.

When trying to track down the post-upgrade apphash divergence we had several hypotheses that we couldn't immediately discount without investigation, and we would like to put mechanisms in place so that these cannot bite us in the future:

• proper build procedure not being run
  • cosmovisor not running the proper build procedure (agd build);
  • yarn build not being run;
• agd script or binary copied to another location
  • non functional ("repoconfig.sh: No such file or directory")
  • even worse, updated agd binary running against previous version of ag-chain-cosmos.

Related to previous issues:

• separate agd build process from runtime files #6455 separate agd build process from runtime files
• ag-chain-cosmos symlink issue #6472 ag-chain-cosmos symlink issue
• Document procedure for isolating and relocating build artifacts #6574 Document procedure for isolating and relocating build artifacts
• Hermetic builds #7052 Hermetic builds