[PECO-AI] PECOBLR-1968: Add warnings in logs if someone uses a connection param that is not defined in python sql connector

[deeksha-db]

PECO Agent Workflow (Partner Ecosystem)

Jira Ticket: https://databricks.atlassian.net/browse/PECOBLR-1968

Changes

Added a KNOWN_KWARGS frozenset constant to client.py listing all supported **kwargs for Connection.__init__. In the constructor, right after the debug log, the code computes set(kwargs.keys()) - KNOWN_KWARGS and emits a logger.warning naming any unrecognized parameter(s). This is a purely additive, backward-compatible change — unknown kwargs continue to be passed through; they just now generate a visible warning.

Test Cases Written

• test_unknown_connection_param_issues_warning — unknown kwarg triggers logger.warning
• test_unknown_connection_param_warning_names_the_param — warning message includes the param name
• `test_known_connection_pa...

Summary: Added a KNOWN_KWARGS frozenset constant to client.py listing all supported **kwargs for Connection.__init__. In the constructor, right after the debug log, the code computes set(kwargs.keys()) - KNOWN_KWARGS and emits a logger.warning naming any unrecognized parameter(s). This is a purely additive, backward-compatible change — unknown kwargs continue to be passed through; they just now generate a visible warning.

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[samikshya-db]

we should add a test test_known_kwargs_is_complete