tools: add block-generator into published build

[tzaffi]

Summary

Adding the block-generator into tools bundle.

Test Plan

Accepting suggestions regarding how to test. Once it's on master and the nightly channel has finished building, we can verify that this worked with the following commands:

❯ LATEST_TOOLS_TAR_BALL=$(aws s3 ls algorand-releases/channel/nightly/ | sort | tail -n 1 | awk '{print $NF}')
❯ echo $LATEST_TOOLS_TAR_BALL
tools_nightly_linux-arm64_3.16.1601.tar.gz

❯ aws s3 cp s3://algorand-releases/channel/nightly/$LATEST_TOOLS_TAR_BALL .
download: s3://algorand-releases/channel/nightly/tools_nightly_linux-arm64_3.16.1601.tar.gz to ./tools_nightly_linux-arm64_3.16.1601.tar.gz

# Inspect that block-generator is in the below list (not here yet...)
❯ tar -tzf $LATEST_TOOLS_TAR_BALL
algons
catchpointdump
cc_agent
cc_client
cc_service
COPYING
coroner
dispenser
dsign
loadgenerator
netgoal
nodecfg
pingpong
sysctl-all.sh
sysctl.sh

[onetechnical]

Seems reasonable...I don't think we test for the presence of these files now.

[tzaffi]

https://app.circleci.com/pipelines/github/algorand/go-algorand/14091/workflows/fee880a4-3267-43db-b001-3b0182265095/jobs/229448?invite=true#step-104-222

[tzaffi]

tar -tzf $LATEST_TOOLS_TAR_BALL

CONFIRMED:

❯ tar -tzf $LATEST_TOOLS_TAR_BALL
algons
block-generator
...