fix: add missing <cstdint> includes

[trofi]

Without the change build fails on this week's gcc-13 as:

In file included from google/cloud/internal/curl_handle.cc:15:
google/cloud/internal/curl_handle.h:107:8:
  error: 'int32_t' in namespace 'std' does not name a type
  107 |   std::int32_t GetResponseCode();
      |        ^~~~~~~

gcc-13 cleaned up <string> not to include <cstdint> for newer c++ standards. Hence the build failures.

---

This change is 

[coryan]

/gcbrun

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[google-cloud-cpp-bot]

Google Cloud Build Logs
For commit: 081386c1fce4a888b188fcc89cb5d0f7a1234da5

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

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

[coryan]

Thanks for the PR! Seems like the robots think you need to sort some headers. The build logs are listed above, but they are tricky to find, so here is a direct link:

https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/10421/081386c1fce4a888b188fcc89cb5d0f7a1234da5/checkers-checkers/log-06f36380-a1f3-4b44-8ea2-f1342a8a712a.txt

Are you using a particular Linux distro to build with GCC 13? I would like to expand our build matrix to cover this case, and I would also like to avoid installing GCC from source.

[trofi]

I'm afraid I'm using locally built gcc-13. Other people used ubuntu's ppa with weekly gcc snapshots, but I'm not familiar with precise locations of those. I wonder if include-what-you-use could provide a similar signal for missing headers.

Applied the following header sorting and force-pushed:

Step #3: -#include <cstdint>
Step #3:  #include <chrono>
Step #3: +#include <cstdint>

Thank you!

[coryan]

/gcbrun

[google-cloud-cpp-bot]

Google Cloud Build Logs
For commit: 3632510adb81f2c52478b4d5b75d43c25670b3c5

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

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

[trofi]

Fixed commit message to match PR (now has fix: ... prefix)

[coryan]

/gcbrun

[google-cloud-cpp-bot]

Google Cloud Build Logs
For commit: 8cca9965feeaf29fbfc4366b53a139e5c639c4b9

• 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.86% // Head: 93.86% // Decreases project coverage by -0.00% ⚠️

Coverage data is based on head (8cca996) compared to base (5af495b).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10421      +/-   ##
==========================================
- Coverage   93.86%   93.86%   -0.01%     
==========================================
  Files        1610     1610              
  Lines      145830   145830              
==========================================
- Hits       136888   136887       -1     
- Misses       8942     8943       +1     

Impacted Files	Coverage Δ
google/cloud/internal/curl_handle.h	100.00% <ø> (ø)
google/cloud/internal/oauth2_credentials.h	33.33% <ø> (ø)
google/cloud/internal/rest_response.h	100.00% <ø> (ø)
google/cloud/pubsub/ack_handler.h	78.57% <ø> (ø)
google/cloud/storage/bucket_cors_entry.h	80.00% <ø> (ø)
google/cloud/storage/internal/hash_function_impl.h	66.66% <ø> (ø)
google/cloud/storage/internal/object_read_source.h	66.66% <ø> (ø)
...bigtable/examples/bigtable_hello_instance_admin.cc	81.00% <0.00%> (-2.00%)	⬇️
google/cloud/bigtable/async_read_stream_test.cc	97.32% <0.00%> (-0.67%)	⬇️
google/cloud/completion_queue_test.cc	97.13% <0.00%> (-0.20%)	⬇️
... and 4 more

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.

[coryan]

Thanks again for the PR