Case-sensitivity in dbt-redshift via `enable_case_sensitive_identifier`

### 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

Not certain the best page. Here are some candidates:
- https://docs.getdbt.com/reference/project-configs/quoting
- https://docs.getdbt.com/docs/core/connect-data-platform/redshift-setup
- https://docs.getdbt.com/reference/resource-configs/redshift-configs

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

https://github.com/dbt-labs/dbt-core/issues/1557#issuecomment-963222118 has helpful insight to some surprising default behavior of Redshift as it relates to case-(in)sensitivity.

The most robust solution is to set the [`enable_case_sensitive_identifier`](https://docs.aws.amazon.com/redshift/latest/dg/r_enable_case_sensitive_identifier.html) parameter to `true` via the AWS [console](https://console.aws.amazon.com/redshiftv2/) or [CLI](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-parameter-groups.html#configure-parameters-using-the-cli) for the Redshift cluster.

### Additional information

The CI tests for https://github.com/dbt-labs/dbt-utils/pull/792 were affected by the default value of `enable_case_sensitive_identifier` being `false`.

This has also affected folks using a combination of Redshift + accepted_values data tests + store_failures / store_failures_as:
- https://github.com/dbt-labs/dbt-adapters/issues/625
- https://github.com/dbt-labs/dbt-core/issues/11443