feat: Private NPM guidance update (#1079)

* feat: Remove bold formatting from feature message, add Callout component for warning message and update configuration section heading

* feat: Update label for private packages and add private-packages.mdx file

website/docs/src/pages/getting-started/_meta.json

@@ -11,5 +11,5 @@
   "usage": "Usage",
   "layout": "Layout",
   "themes": "Themes",
-  "private-packages": { "title": "Private packages", "label": "Pro" }
+  "private-packages": { "title": "Private packages", "label": "Enterprise" }
 }

website/docs/src/pages/getting-started/private-packages.mdx

@@ -1,8 +1,16 @@
+import { Callout } from 'nextra-theme-docs'
+
 # Private packages
 
 With Sandpack, you can securely consume private npm registries (GitHub packages, npm private registry, custom registries, etc.) within just a few steps. A CodeSandbox internal proxy provides the interface to communicate with a custom private npm registry and retrieve npm packages from any npm registry. 
 
-**This feature is available for all Team Pro accounts, and you can access the settings [here](https://codesandbox.io/dashboard/settings/npm-registry).**
+You can access the settings [here](https://codesandbox.io/dashboard/settings/npm-registry).
+
+<Callout emoji="⚠️">
+This setting is only available on enterprise plans.
+</Callout>
+
+## Configuration
 
 ## Get started