STeve (Xin) Huang

This also fixed an issue on Mac for me, where the launched command (`os.Exec`) **within** the prompt does not print out stdin.

Workarounds, please use auto-discovery or dynamic resources.

I couldn't reproduce this with v15.3.0 fips build. ``` storage: region: us-east-1 audit_sessions_uri: "s3:///root-cluster" ``` Debugging locally with AWS log shows it's using the right fips URL in the `https://bucket.s3-fips.us-east-2.amazonaws.com`...

The problem was resolved in user cluster when moved to a new bucket. We suspected the issue is that the previous bucket has dot `.` in the name.

@GavinFrazar @Tener could you take a quick look at the databases that you are familiar with/worked on? Thanks!

https://console.cloud.google.com/cloud-build/builds/d53d35e8-be41-4970-a731-f6b6d9184f8c?project=ci-account

Agreed that the current modes are convoluted. I think we should do an RFD update ([0068](https://github.com/gravitational/teleport/blob/master/rfd/0068-session-recording-modes.md)) to discuss the desired behaviour and UX.

> Is there a reason why we're not using [cloud.google.com/go/cloudsqlconn](https://pkg.go.dev/cloud.google.com/go/cloudsqlconn) and [cloud.google.com/go/alloydbconn](https://pkg.go.dev/cloud.google.com/go/alloydbconn)? Part of not-using-the-connector-lib is to support the case to authenticate as a different database user for change feed....

Converted to draft to try out the connector lib

@espadolini updated the PR now to use the connector lib. sample usage see preview of doc draft https://docs-qhi80m1z1-goteleport.vercel.app/docs/reference/backends/#google-cloud-iam-authentication. Opening for review again.