docs(core): add cacheKeyPrefix option to s3 remote cache options (#34157)

This pull request updates the documentation for the S3 cache plugin to
add the missing `cacheKeyPrefix` setting.

Text taken from #31395

Fixes #34147

---------

Co-authored-by: Caleb Ukle <caleb@nrwl.io>
Co-authored-by: Caleb Ukle <caleb.ukle+github@pm.me>
Co-authored-by: Simon Heather <simon.heather@yulife.com>

Author: 3 people

astro-docs/src/content/docs/reference/Remote Cache Plugins/s3-cache/overview.mdoc

@@ -208,6 +208,7 @@ If you are using MinIO earlier than `2024-07-04T14-25-45Z` it is recommended to
 | **accessKeyId**     | AWS Access Key ID (optional if `AWS_ACCESS_KEY_ID` is set in the environment)                             |
 | **secretAccessKey** | AWS secret access key (optional if `AWS_SECRET_ACCESS_KEY` is set in the environment)                     |
 | **disableChecksum** | This disables AWS' checksum validation for cache entries                                                  |
+| **cacheKeyPrefix**  | Prefix added to cache keys                                                                                |
 
 By default, Nx will try to write and read from the remote cache while running locally. This means that permissions must be set for users who are expected to access the remote cache.
 
@@ -237,6 +238,19 @@ The cache mode in CI can also be configured by setting `ciMode` to `read-only` o
 }
 ```
 
+# Cache Key Prefix
+
+The `cacheKeyPrefix` setting enables you to add a prefix to your cache keys, making it possible to store multiple projects or environments within the same storage bucket.
+
+```jsonc
+// nx.json
+{
+  "s3": {
+    "cacheKeyPrefix": "designSystem",
+  },
+}
+```
+
 ### Migrating from Custom Tasks Runners
 
 Many people who are interested in Nx caching plugins have previously used custom task runners. Nx offers a new and simpler extension API designed to meet the same use cases as the now-deprecated custom task runners.