Add DEBUG log on compile and verify insertmanyvalues path

- Adds a single DEBUG-level log in DatabricksStatementCompiler.__init__
  recording the template and the compiled SQL. Fires once per
  compilation, only when sqlalchemy logging is at DEBUG. Quiet at
  default log levels — no per-bindparam noise.

- Empirically verified the _deliver_insertmanyvalues_batches code path
  (compiler.py:5648) works with the backticked template. Flipping
  use_insertmanyvalues=True and bulk-inserting 20 rows into a table
  with a hyphenated column produced the expected SQL
  (:`id__0`, :`col-name__0`, ...) logged as "generated in X
  (insertmanyvalues)" by SQLAlchemy, and all 20 rows round-tripped.

Co-authored-by: Isaac

Author: msrathore-db

src/databricks/sqlalchemy/_ddl.py

@@ -120,6 +120,18 @@ class DatabricksStatementCompiler(compiler.SQLCompiler):
     bindtemplate = property(lambda self: self._BIND_TEMPLATE, lambda self, _: None)
     compilation_bindtemplate = property(lambda self: self._BIND_TEMPLATE, lambda self, _: None)
 
+    def __init__(self, *args, **kwargs):
+        super().__init__(*args, **kwargs)
+        # One-line trace of what we rendered — helps debug reported SQL
+        # issues without adding per-bindparam noise.
+        if logger.isEnabledFor(logging.DEBUG):
+            logger.debug(
+                "DatabricksStatementCompiler compiled statement with "
+                "backtick-quoted bind markers (template=%s): %s",
+                self._BIND_TEMPLATE,
+                self.string,
+            )
+
     def limit_clause(self, select, **kw):
         """Identical to the default implementation of SQLCompiler.limit_clause except it writes LIMIT ALL instead of LIMIT -1,
         since Databricks SQL doesn't support the latter.