fix(all): use CheckResponse for media downloads

[codyoss]

If a method supports media downloads use CheckResponse. This method
provided extra context to errors if the api follow
https://google.aip.dev/193. The storage api will continue to use
CheckMediaResponse as it does not conform to the aip due to legacy
reasons.

Fixes: #752

[codyoss]

Ran the generator on cached discovery docs to generate the changes.

[tbpg]

Just to confirm, do we have sufficient test coverage to be confident these are still working properly?

[codyoss]

Yup, everything should work just fine. We could probably get away with removing CheckMediaResponse all together in the future. CheckResponse's only real difference is it will try to json.Unmarshall the value into something more descriptive. If the unmarshalling fails it falls back to the old behavior. At worst you lose some performance on error cases.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.