Add info about CLL data platform support (#4925)

## What are you changing in this pull request and why?

Add info about CLL data platform support in the **Caveats** section of
the CLL page

## Checklist
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [x] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [x] Needs PM review

website/docs/docs/collaborate/column-level-lineage.md

@@ -41,6 +41,10 @@ When exploring your data products, navigating column lineage allows analytics en
 
 ## Caveats
 
+Following are the CLL caveats/limitations. 
+
+### SQL parsing
+
 Column-level lineage relies on SQL parsing. Errors can occur when parsing fails or a column's origin is unknown (like with JSON unpacking, lateral joins, and so on). In these cases, lineage may be incomplete and dbt Cloud will provide a warning about it in the column lineage. 
 
 <Lightbox src="/img/docs/collaborate/dbt-explorer/example-parsing-error-pill.png" title="Example of warning in the full lineage graph"/>
@@ -54,3 +58,17 @@ Possible error cases are:
 - **Parsing error** &mdash; Error occurs when the SQL is ambiguous or too complex for parsing. An example of ambiguous parsing scenarios are _complex_ lateral joins.
 - **Python error** &mdash; Error occurs when a Python model is used within the lineage. Due to the nature of Python models, it's not possible to parse and determine the lineage.
 - **Unknown error** &mdash; Error occurs when the lineage can't be determined for an unknown reason. An example of this would be if a dbt best practice is not being followed, like using hardcoded table names instead of `ref` statements.
+
+### Data platform support
+
+CLL in dbt Cloud works with the following data platforms: 
+- Snowflake
+- BigQuery
+- Redshift
+- Databricks (Unity Catalog) 
+
+The following adapters aren't currently supported by CLL in dbt Cloud. More of these platforms will be supported in the future. 
+- Hive metastore version of Databricks
+- Apache Spark
+- Starburst/Trino
+- Microsoft Fabric