Make environs/bootstrap responsible for tools location

environs/bootstrap now finds available tools, augmenting or substituting
for locally buildable/uploadable tools as necessary (auto upload) or as
specified (--upload-tools). Environ.Bootstrap is now provided with a list
of available tools, and is not responsible for syncing tools itself.

--upload-series and --series are obsoleted: we upload a single series,
and then clone that for each supported series. When we store the tools
catalogue in state, we will simply write an entry for each series that
points to the same tools tarball.
We can't tell what the provider will pick, so we need to make them all available up front.

I'll change this a bit so we only call validateUploadAllowed if there are locally buildable tools that don't exist in the ones found externally.