Add proxy config to debug log

[keisku]

What does this PR do?

Add proxy config to debug log. Otherwise, it is same as the previous log.

2022-09-21 05:25:21 UTC | CORE | DEBUG | (pkg/collector/python/datadog_agent.go:128 in LogMessage) | http_check:datadoghq:c32caf18e275e4fa | (http_check.py:109) | Connecting to https://www.datadoghq.com/with proxy config, {'http': 'http://127.0.0.1', 'https': 'http://127.0.0.1', 'no': ['127.0.0.1', 'localhost']}

2022-09-21 05:42:23 UTC | CORE | DEBUG | (pkg/collector/python/datadog_agent.go:128 in LogMessage) | http_check:datadoghq:c32caf18e275e4fa | (http_check.py:109) | Connecting to https://www.datadoghq.com/with proxy config, {'http': 'http://127.0.0.1', 'https': '', 'no': ['127.0.0.1', 'localhost']}

Motivation

Debug log with proxy config would help identifying the root cause of http_check failure. Proxy sometimes can be a root cause of it.

Additional Notes

Review checklist (to be filled by reviewers)

• [ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• [ ] PR title must be written as a CHANGELOG entry (see why)
• [ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
• [ ] PR must have changelog/ and integration/ labels attached

[codecov[bot]]

Codecov Report

Merging #12988 (66efa30) into master (0b92164) will increase coverage by 0.01%. The diff coverage is 100.00%.

Flag	Coverage Δ
http_check	95.38% <100.00%> (+2.08%)	:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.