[Bug] Connection PID Query Causes unnecessary Serverless Billing

[jaswanthikolla]

Is this a new bug in dbt-redshift?

• I believe this is a new bug in dbt-redshift
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

In Redshift Serverless, Queries are billed for a minimum of 60 seconds, and they are not billed from connection time. But, This query is executed right at the connection creation ( Let's say T0) before executing the first query(T1). This causes the Serverless Redshift to start the queries timer at T0 instead of first query T1, causing the unnecessary billing for T1 - T0 time period.

Expected Behavior

This query should be executed right before executing the first query on the connection. If the PID aleady exists, there is no need to do it again.

Steps To Reproduce

1. Configure DBT profile with Redshift Serverless
2. Open a Connection, and note down the time as T0
3. Execute a user query, and note down the time as T1
4. Validate that billing starts from by validating it against table: SYS_SERVERLESS_USAGE

Relevant log output

No response

Environment

- OS: NA
- Python: NA
- dbt-core: main 
- dbt-redshift: Main

Additional Context

No response

[amychen1776]

Closing this one to consolidate issues!