fix(logging): do not panic in library code

[0xSage]

fixes: #1862

Changes:

• No longer panic on User introduced errors. Instead we log the error and let program proceed
• We log.Fatalf("ptypes.TimestampProto(time.Unix(0,0)) failed: %v", err) to exit program, since it's a fatal error/likely not induced by Users

[gcf-merge-on-green]

Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR

[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.

[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.

[0xSage]

After careful consideration:

1. When r.Request is nil, we pipe error message to errc like @tbpg suggested!

2. When protoStruct contains non-parseable but VALID JSON, we don't log to user at all because i) they will already know a property didn't parse correctly (see a nil value) ii) It's not a user error and there's nothing the user can do to solve this issue. So we don't log per client library convention to be less verbose.

"libraries shouldn't log" :)

[0xSage]

@codyoss ready for your review on previous change requested, thanks!

[codyoss]

LGTM