Upgrade closure-builder to fix #183.

[mikelehen]

Josh, this should fix #183. Thoughts about including it in this week's release?

Also, I don't really understand why extra stuff in yarn.lock changed. Let me know if you think it's problematic.

[jshcrowthe]

Sounds good! I'll stage the release for testing after merging this.

The yarn.lock is updated as it fixed the version of closure builder to the specific patch. It being updated here is to be expected.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

[mikelehen]

Yeah, I expected closure-builder to change in yarn.lock, but there were several other diffs too. Perhaps those were dependencies of closure-builder or something though. I'm not sure.