impl(common): helpers to create ErrorInfo

[coryan]

Motivated by #5915

---

This change is 

[google-cloud-cpp-bot]

Google Cloud Build Logs
For commit: 6e94f9ab7875b5b1bd0449de168b97c15b39d79a

• Public Access Build Logs
• Cloud Build Console (requires auth)
• Kokoro Logs (requires auth)

ℹ️ NOTE: Kokoro logs are linked from "Details" below.

[codecov]

Codecov Report

Base: 93.82% // Head: 93.82% // No change to project coverage 👍

Coverage data is based on head (98e6839) compared to base (98e6839).
Patch has no changes to coverable lines.

❗ Current head 98e6839 differs from pull request most recent head 6e94f9a. Consider uploading reports for the commit 6e94f9a to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10271   +/-   ##
=======================================
  Coverage   93.82%   93.82%           
=======================================
  Files        1570     1570           
  Lines      143816   143816           
=======================================
  Hits       134930   134930           
  Misses       8886     8886           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[scotthart]

Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on @coryan)

---

google/cloud/internal/make_status_test.cc line 135 at r1 (raw file):

}

TEST(MakeStatus, WithErrorInfo) {

I'm curious why not use gTest's INSTANTIATE_TEST_P to do these parameterized tests?

[scotthart]

Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @coryan)

[coryan]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @scotthart)

---

google/cloud/internal/make_status_test.cc line 135 at r1 (raw file):

Previously, scotthart (Scott Hart) wrote…

I'm curious why not use gTest's INSTANTIATE_TEST_P to do these parameterized tests?

I keep that at the bottom of the toolbox. For not particular reason.