docs: added pnpm catalogs (#10463)

### Description

Added [pnpm catalogs](https://pnpm.io/catalogs) as another option to
keep dependency versions in sync across packages.

### Testing Instructions

None, just docs.
<!--
  Give a quick description of steps to test your changes.
-->

---------

Co-authored-by: Anthony Shew <[email protected]>

Author: mrr11k

docs/site/content/docs/crafting-your-repository/managing-dependencies.mdx

@@ -180,10 +180,12 @@ You can use your package manager to update dependency versions in one command.
 <PackageManagerTabs>
 
 <Tab value="pnpm">
+
 ```bash title="Terminal"
 pnpm up --recursive typescript@latest
 ```
-  <small>[→ pnpm documentation](https://pnpm.io/cli/update#--recursive--r)</small>
+
+<small>[→ pnpm documentation](https://pnpm.io/cli/update#--recursive--r)</small>
 
 </Tab>
 
@@ -220,6 +222,12 @@ No equivalent
 </Tab>
 </PackageManagerTabs>
 
+#### pnpm catalogs
+
+In pnpm v9.5+, you can use catalogs to define dependency version ranges as reusable constants. This will keep dependencies on the same version since you're referencing the same value across the workspace.
+
+To learn more, [visit the pnpm catalogs documentation](https://pnpm.io/catalogs).
+
 #### Using an IDE
 
 Your IDE's refactoring tooling can find and replace the version of a dependency across all `package.json` files in your repository at once. Try using a regex like `"next": ".*"` on `package.json` files to find all instances of the `next` package and replace them with the version you want. When you're done, make sure to run your package manager's install command to update your lockfile.