Remove unsafe LOG() call in destructor/shutdown disconnect path

LOG() internally acquires the GIL via py::gil_scoped_acquire, which is
unsafe during interpreter shutdown or stack unwinding — it can deadlock
or trigger std::terminate(). Replace with a comment explaining why
logging is intentionally skipped.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: saurabh500

mssql_python/pybind/connection/connection.cpp

@@ -164,7 +164,9 @@ void Connection::disconnect() {
         if (hasGil) {
             checkError(ret);
         } else if (!SQL_SUCCEEDED(ret)) {
-            LOG("SQLDisconnect failed in destructor/shutdown path; ignoring error");
+            // Intentionally no LOG() here: LOG() acquires the GIL internally
+            // via py::gil_scoped_acquire, which is unsafe during interpreter
+            // shutdown or stack unwinding (can deadlock or call std::terminate).
         }
         // triggers SQLFreeHandle via destructor, if last owner
         _dbcHandle.reset();