Link to reference docs for the target-path configuration (#4922)

[Preview](https://docs-getdbt-com-git-dbeatty-target-path-for-artifacts-dbt-labs.vercel.app/docs/dbt-cloud-apis/sl-manifest)

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

While working on #4921,
I noticed an opportunity to link to the docs that show how to configure
the target path for artifacts (like `semantic_manifest.json`

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

website/docs/docs/dbt-cloud-apis/sl-manifest.md

@@ -19,7 +19,7 @@ dbt creates an [artifact](/reference/artifacts/dbt-artifacts) file called the _S
 
 By using the semantic manifest produced by dbt Core, MetricFlow will instantiate a data flow plan and generate SQL from Semantic Layer query requests. It's a valuable reference that you can use to understand the structure and details of your data models.
 
-Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` also lives in the `/target` directory of your dbt project. This is where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
+Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` file also lives in the [target directory](/reference/project-configs/target-path) of your dbt project where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
 
 ## How it's produced