Update data-test-configs.md (#5901)

## What are you changing in this pull request and why?
This should be removed from the docs page because the implementation is
not ready to be shipped yet

## Checklist
<!--
Uncomment when publishing docs for a prerelease version of dbt:
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
- [ ] 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.
- [ ] 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).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/vercel.json`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages

website/docs/reference/data-test-configs.md

@@ -275,30 +275,3 @@ tests:
 ```
 
 </File>
-
-#### Specify custom configurations for generic data tests
-
-:::note 
-
-This functionality is supported on ["Versionless"](/docs/dbt-versions/upgrade-dbt-version-in-cloud#versionless). Specifying custom configurations for data tests will become available in dbt Core v1.9, available later this year.
-
-:::
-
-Use any custom config key to specify custom configurations for data tests. For example, the following specifies the `snowflake_warehouse` custom config that dbt should use when executing the `accepted_values` data test:
-
-```yml
-
-models:
-  - name: my_model
-    columns:
-      - name: color
-        tests:
-          - accepted_values:
-              values: ['blue', 'red']
-              config:
-                severity: warn
-                snowflake_warehouse: my_warehouse
-
-```
-
-Given the config, the data test runs on a different Snowflake virtual warehouse than the one in your default connection to enable better price-performance with a different warehouse size or more granular cost allocation and visibility.