feat(http): improve error logging with client IP

[maximk777]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

Closes #7328

What's changed and what's your intention?

This PR improves HTTP error logging as requested in #7328.

1. ErrorResponse::from_error_message() now logs errors (error_result.rs)

Previously, from_error_message() created error responses without logging, while from_error() did log. This meant handlers using from_error_message() directly bypassed the logging mechanism.
Now both methods log consistently:

• error! level for server errors (where should_log_error() returns true)
• debug! level for client errors (e.g., InvalidArguments)

2. New middleware log_error_with_client_ip (client_ip.rs)

Added middleware that logs all 4xx/5xx responses with client IP address.

3. Enabled ConnectInfo in HTTP server (http.rs)

Changed into_make_service() to into_make_service_with_connect_info::() to make client IP available in request extensions.

Limitations:

Client IP may not be available in tests (middleware handles this gracefully by logging without IP)

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.

  Logging behavior was verified manually.

• This PR requires documentation updates. (Not required - internal changes only)
• API changes are backward compatible.
• Schema or data changes are backward compatible.

[yihong0618]

I think we add a new function here, add a unittest for it would be better

[maximk777]

Done! Added unit tests for the middleware.

[evenyag]

I have also found one place missing the error log:

greptimedb/src/servers/src/http/result/prometheus_resp.rs

Lines 67 to 76 in 9343da7

	impl IntoResponse for PrometheusJsonResponse {
	fn into_response(self) -> Response {
	let metrics = if self.resp_metrics.is_empty() {
	None
	} else {
	serde_json::to_string(&self.resp_metrics).ok()
	};
	let http_code = self.status_code.map(|c| status_code_to_http_status(&c));

Could you also add it for the PrometheusJsonResponse?

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 44166133cf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move client-IP error logger ahead of auth short-circuit

Placing log_error_with_client_ip after the auth middleware means any response that authorize::check_http_auth returns directly (for example 401/403 from missing or invalid credentials) never reaches this logger, so those error responses are not logged with client address. This is a behavior gap for real traffic where auth rejects requests, and it contradicts the intended “log 4xx/5xx with client IP” coverage.

Useful? React with 👍 / 👎.