fix: redact sensitive data from evaluation SDK log messages

[slister1001]

Description

Redacts user-provided content (queries, responses, tool definitions, exception messages) from log strings in azure-ai-evaluation that flow into Geneva telemetry (ViennaExp/Log). This prevents database connection strings and other credentials embedded in user payloads from being flagged by CredScan.

Resolves ICM 738457593

Changes

• utils.py - Remove f-string interpolation of query, response, tool_definitions, and exception from log messages
• Downgrade noisy agent-response fallback warnings to logger.debug
• Sanitize upload error to emit only type(e).__name__ instead of full exception text
• Chain original exception with from e for proper traceback

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes. (N/A - no user-facing behavior change)
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message.

Testing Guidelines

• Pull request includes test coverage for the included changes. (Log message changes only - no behavioral change to test)

[Copilot]

Pull request overview

This PR addresses a critical security issue by redacting sensitive user-provided data from log messages in the azure-ai-evaluation SDK that flow into Geneva telemetry. The changes prevent database connection strings and other credentials embedded in user payloads from being exposed in logs and flagged by CredScan tools.

Changes:

• Removed user-provided content (queries, responses, tool definitions) from log message strings
• Downgraded noisy agent-response fallback warnings from logger.warning to logger.debug
• Sanitized upload error messages to emit only exception type names instead of full exception text
• Added proper exception chaining with from e for maintaining traceback while keeping logs clean

[Copilot]

The bare except: clause should specify Exception to avoid catching system-exiting exceptions like KeyboardInterrupt and SystemExit. This is inconsistent with the exception handling patterns used elsewhere in the file (see lines 700 and 786 which use except Exception as e:). Consider changing this to except Exception: for consistency and better practice.