[BUG] Snowflake Connect action (execute-sql-query) fails

**Describe the bug**
The Pipedream Connect snowflake-execute-sql-query action does not work for Snowflake connections using key-pair authentication. Two distinct failures observed:

1. Direct action execution (shared static IP disabled)
The snowflake-sdk@2.3.6 bundled in components/snowflake sends a malformed login request that Snowflake rejects with HTTP 400 (RequestFailedError, code 401002). The action reaches Snowflake (OCSP check succeeds, login POST is made) but the request payload is rejected at the protocol level.

2. Action execution with shared static IP enabled
When shared static IP is turned on for the Connect project, actions route through Pipedream's SQL proxy. The proxy returns HTTP 502 with "Snowflake connection is not valid" for key-pair auth connections. The request never reaches Snowflake.

Impact
Because Connect actions cannot execute Snowflake queries, the consuming service (Pivot) must call get_account_credentials(include_credentials=True) to retrieve raw credentials and connect to Snowflake directly. This means credentials transit through the consuming service's memory, which is a concern flagged in a security review. If either the SDK login or the SQL proxy's key-pair auth support is fixed, credentials would never need to leave Pipedream.

Reproduction
- Pipedream Connect project with a Snowflake connection using key-pair auth (private key + passphrase)
- Call actions.run(id="snowflake-execute-sql-query", ...) via the Python SDK
- Snowflake network policy open to allow Pipedream IPs
- Tested 2026-08-28, snowflake-sdk@^2.3.6