chore: change request log level in proxy

[CooooolFrog]

Description

This PR addresses a potential security problem mentioned in this issue (#1559) by changing the output logs for request-related data from the info level to the debug level, thus preventing the direct output of sensitive information.

Related Issue

#1559

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.26%. Comparing base (c70d810) to head (42a2902).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1710      +/-   ##
==========================================
- Coverage   50.29%   50.26%   -0.04%     
==========================================
  Files          86       86              
  Lines       21952    21952              
==========================================
- Hits        11041    11034       -7     
- Misses      10911    10918       +7     

Files with missing lines	Coverage Δ
dragonfly-client/src/proxy/mod.rs	0.00% <ø> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

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

[jim3ma]

LGTM

[gaius-qi]

I think the key download information should be kept, but we can remove the request headers when printing. The log output level still needs to be set to INFO.

[CooooolFrog]

I think the key download information should be kept, but we can remove the request headers when printing. The log output level still needs to be set to INFO.

This is better. I'll modify it again: output the part of the request excluding the header at the Info level, and output the header separately at the debug level.

[CooooolFrog]

I misused git force push, which closed this PR. Please continue reviewing in this new PR.
#1715