docs: prep for v2 documentation (#6710)

This PR includes documentation that preps for v2 docs (but doesn't introduce new docs).

_Note: The number of file changes in the PR is due to find-and-replace within the `references` which is unavoidable. Let me know if I should move it to another PR._

## Changes

- Change Medusa version in base OAS used for v2.
- Fix to docblock generator related to not catching all path parameters.
- Added typedoc plugin that generates ER Diagrams, which will be used specifically for data model references in commerce modules.
- Changed OAS tool to output references in `www/apps/api-reference/specs-v2` directory when the `--v2` option is used.
- Added a version switcher to the API reference to switch between V1 and V2. This switcher is enabled by an environment variable, so it won't be visible/usable at the moment.
- Upgraded docusaurus to v3.0.1
- Added new Vale rules to ensure correct spelling of Medusa Admin and module names.
- Added new components to the `docs-ui` package that will be used in future documentation changes.

www/apps/docs/content/modules/orders/fulfillments.md

@@ -21,7 +21,7 @@ When a fulfillment is created for one or more item, shipments can then be create
 Some of the `Fulfillment` entity’s attributes include:
 
 - `provider_id`: a string indicating the ID of the fulfillment provider that processes this fulfillment. You can also access the provider by expanding the `provider` relation and accessing `fulfillment.provider`.
-- `location_id`: a string indicating where the fulfillment is being made from. When paired with the Stock Location module in the Medusa backend, this would be the ID of a `StockLocation`.
+- `location_id`: a string indicating where the fulfillment is being made from. When paired with the Stock Location Module in the Medusa backend, this would be the ID of a `StockLocation`.
 - `no_notification`: a boolean value indicating whether the customer should receive notifications for fulfillment updates.
 - `data`: an object that can hold any data relevant for the fulfillment provider.
 - `shipped_at`: a date indicating when the fulfillment was shipped.

www/apps/docs/content/modules/orders/overview.mdx

@@ -48,7 +48,7 @@ Customers can view their previous orders.
     label: 'User Guide: Export Orders',
     customProps: {
       icon: Icons['users-solid'],
-      description: 'Export orders into CSV files in Medusa admin.'
+      description: 'Export orders into CSV files in Medusa Admin.'
     }
   },
 ]} />

www/apps/docs/content/modules/orders/storefront/handle-order-edits.mdx

@@ -200,7 +200,7 @@ In case the customer wants to confirm the order edit, you must check whether a r
 
 ### Refund Amount
 
-If `difference_due` is less than 0, then the amount will be refunded to the customer by the merchant from the Medusa admin. No additional actions are required here before [completing the order edit](#complete-the-order-edit).
+If `difference_due` is less than 0, then the amount will be refunded to the customer by the merchant from the Medusa Admin. No additional actions are required here before [completing the order edit](#complete-the-order-edit).
 
 ### Make Additional Payments