annotated_run.py and remote_run.py both have fallback paths for LogDog bootstrapping. These paths are engaged when LogDog decides that it is enabled, but fails to bootstrap successfully, either due to an infrastructure failure early in bootstrapping or due to bootstrap configuration.

LogDog has been deployed for over a year now, and is believed to be stable enough to remove this fallback. We should make it so that, if LogDog is engaged, its failure is considered a build failure.

This is important because:
- Systems now rely on log data being present in LogDog, and this dependency should not randomly fail if something went wrong.
- The "perf*" waterfalls are now using LogDog log export to impose security, and a fallback would be a breach of this.