The SCons build features a spinner that essentially lets the user know things are happening. This is implemented on our SConstruct via the SCons API Progress class. This progress class only updates when scons build nodes are processed. During the bazel migration, we are doing a lot of intermittent queries to bazel which are outside of what this Progress class would normally cover.

We should implement a basic spinner which covers the gaps of the Progress spinner. The default progress spinner activates after scons starts "Building targets...", so we should supplement during the SConscript reading phase with our own spinner print out, specifically because the extra time waiting doing bazel queries to get build information out of bazel.