Unify cloud and core data platform connection auth wording

[mirnawong1]

Contributions

• [X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

Per slack thread, Erin raised user confusion between different terminology used in the 'set up data platform' core docs and 'set up data platform' cloud docs.

• Users aren't seeing the same data platform auth parity in cloud vs core
• The breakdown of ways to connect Redshift to cloud isn’t mirrored in the cloud docs (if we talk about password and IAM access in core, it would be helpful to use the same wording and talk about what is possible and what isn’t so it is clear)

specific example

The specific callout Erin raised was a core user who uses Redshift and transitioning to cloud. but for dbt Cloud Redshift connection, we don’t use the same terminology. the user is coming from setting up core during his exploration and wanted to know if he has the ability to switch between password and IAM access in dbt Cloud the same way he was able to do in Core

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-starburst-trino https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-snowflake https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-bigquery https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-databricks https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-apache-spark

Additional information

These are the dbt Core data platform set up docs

[runleonarun]

Are these the authentication docs we want to surface in the cloud connection docs? Should we create a reusable for this?

[mirnawong1]

i think it's the dbt core 'connect to data platform' docs -- i'll update the issue above!