enhancement: Verbose Test Harness

[tzaffi]

Summary

To improve visibility of C.I. build failures, utilize new logging capabilities in the sandbox (algorand/sandbox#181) and set VERBOSE_HARNESS=1.

In particular we can now see:

• traces of the docker compose up command
• dumped docker-compose logs for:
  • indexer-db
  • algod
  • indexer

TODO

• open similar PR's in the other SDK's
• Wait for algod: State delta endpoints  #538 to get merged
• Wait for docker-compose log dumps when verbose algorand-sdk-testing#288 to get merged

What does a successful build look like?

See for example this build. You'll need to download Circle's log as the max display at Circle is 400K characters.

What does a failed build look like?

As a test case I pinned the companion algorand-sdk-testing PR (algorand/algorand-sdk-testing#288) to a broken indexer commit. The build broke early enough to see the entire logs directly on circle. There are two highlights to look for:

1. We can see the usual error information one or more services failed to start
2. Then the docker compose logs are dumped for each of the services and at the end we see could not load genesis...

[Eric-Warehime]

LGTM, you just need to update the sdk testing branch to master

[winder]

LGTM, just need to update the branch.

[algochoi]

LGTM, thanks! very helpful for debugging