feat(gax): bump version to 1.8

[vsharonlynn]

Bumps google-cloud-gax to 1.7

Splitting version bump from PR #4601 as requested in this comment.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.07%. Comparing base (dc8585f) to head (fcc6df0).
⚠️ Report is 109 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4695      +/-   ##
==========================================
+ Coverage   95.06%   95.07%   +0.01%     
==========================================
  Files         198      198              
  Lines        7598     7598              
==========================================
+ Hits         7223     7224       +1     
+ Misses        375      374       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coryan]

Bumps google-cloud-gax to 1.7

This is a good idea, but won't help with this comment:

Splitting version bump from PR #4601 as requested in this comment.

*-gax@1.7 was recently released. You are about to add new functionality (which will require a bump to 1.8) and then use a new functionality in *-gax-internal. You will need to bump this again to 1.8 when that happens.

[coryan]

Sorry, I should have thought of this earlier. It may be easier to follow the instructions here:

https://github.com/googleapis/google-cloud-rust/blob/main/doc/contributor/howto-guide-generated-code-maintenance.md#bump-all-version-numbers

In general, it may be better to start by adding the functionality to google-cloud-gax and then bumping the version numbers. Otherwise we signal to consumers of the crate that something changed, when it has not.

[coryan]

Let me know if you would rather merge these manual changes or try the how-to guide. I am fine with either.

[vsharonlynn]

Sorry, I should have thought of this earlier. It may be easier to follow the instructions here:

https://github.com/googleapis/google-cloud-rust/blob/main/doc/contributor/howto-guide-generated-code-maintenance.md#bump-all-version-numbers

In general, it may be better to start by adding the functionality to google-cloud-gax and then bumping the version numbers. Otherwise we signal to consumers of the crate that something changed, when it has not.

Ok! We will do this in order:

1. @joshuatants will submit the functionalities.
2. I will use the how-to guide to bump the version number for gax library.

Thanks @coryan !

Will approve again once the new functionality is in.

[coryan]

Closing, this won't be needed with the approach in #4839. You can reopen if needed.