Database connection failed for database that uses LOGMETH=LDAP

[AaronLu71]

Describe the bug
I was trying to use Docker compose to spin up the server. The server set up successfully and accessible, but when calling the query tools (e.g. base_readQuery), it depends on the LOGMETH the database is configured for. If the database uses LOGMETH=LDAP, there was an error message saying: "Invalid Username or Password..." and if the database uses LOGMETH=TD2, then query ran successfully (yes, I tried 2 different databases). So, I suspect that the LOGMETH setting is overridden by the default TD2 somewhere, because I know if I used TD2 for DB that uses LDAP, I would get the same error message. There was no such issue in previous versions though.

To Reproduce
Steps to reproduce the behavior:

1. use the following docker-compose.yml
   services:
   teradata-mcp-server:
   build:
   context: .
   args:
   - ENABLE_FS_MODULE=${ENABLE_FS_MODULE:-false}
   - ENABLE_EVS_MODULE=${ENABLE_EVS_MODULE:-false}
   image: teradata-mcp-server:latest
   environment:
   • DATABASE_URI=teradata://user:pwd@server:1025/database
   • LOGMECH=LDAP
   • MCP_TRANSPORT=streamable-http
   • MCP_PATH=/mcp/
   • MCP_HOST=0.0.0.0
   • MCP_PORT=8001
   • PROFILE=dataScientist
     ports:
   • "${PORT:-8001}:8001"
2. when calling base_readQuery tool, you will get error: "Invalid Username or Password..."

Expected behavior
When use LOGMECH=LDAP in docker compose. MCP server should successfully connect to the database that uses LDAP log in mechanism.

[dtehan-td]

@AaronLu71 fix has been submitted and tested. Thanks for raising this issue.