fix: force http1 only

[PhongChuong]

Force reqwest to use http1 only as we currently do not support HTTP2 in our clients.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.84%. Comparing base (f6a578e) to head (bbc57df).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4296   +/-   ##
=======================================
  Coverage   94.84%   94.84%           
=======================================
  Files         187      187           
  Lines        7194     7195    +1     
=======================================
+ Hits         6823     6824    +1     
  Misses        371      371           

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

[PhongChuong]

Note: I was able to manually test this with @dbolduc repro instructions. However, I couldn't find a good place to automate the testing since it requires adding the "http2" feature to reqwest in the cargo.toml. Any pointer in that regard is welcomed.

[coryan]

Note: I was able to manually test this with @dbolduc repro instructions. However, I couldn't find a good place to automate the testing since it requires adding the "http2" feature to reqwest in the cargo.toml. Any pointer in that regard is welcomed.

I think you would need a new integration test crate that enables that feature, and you would need to run that with cargo test --package new-crate-name. Make sure the new crate is not in the default-members list. If you try to add this to an existing crate all the tests in that crate would gain the feature. And if it is in the default-members list then any cargo test would include them and enable the feature for everybody else too.