Tests should pass when run with go test, with or without GOLANG_SAMPLES_PROJECT_ID.

Some of these should legit fail due to API not being enabled on the test project, etc. but they have confusing test output, including some that panic, leaving a large stack trace to dig through.

$ GOLANG_SAMPLES_PROJECT_ID=cbro-scratch go test -v ./...

<snip>

asset:

=== RUN   TestM

Description

In order to make it easier for developers to identify asynchronous methods, the following conventions need to be introduced:

1. Use of "async" keyword in the function definitions.
2. Use of "Async" added to the end of the function name.

E.g.

Before changes:

fetchClassroomData(classroomUrlFragment: string): Promise<ClassroomData> {
  return new Promise((resolve, 

We should let user know there was unhandled error on server.

Especially useful during development.