docs: fix broken links utility + uncaught broken links (#12637)

* fix broken links

* update broken links utility

* add missing payment evens

* generate llms

* fix segment link

www/apps/resources/app/recipes/bundled-products/examples/standard/page.mdx

@@ -1756,7 +1756,7 @@ The add-to-cart workflow for bundled products has the following steps:
         type: "step",
         description: "Add the items in the bundle to the cart.",
         depth: 1,
-        link: "/references/workflows/addToCartWorkflow"
+        link: "/references/medusa-workflows/addToCartWorkflow"
       },
       {
         name: "useQueryGraphStep",
@@ -2778,7 +2778,7 @@ The workflow has the following steps:
         type: "workflow",
         description: "Remove the items in the bundle from the cart.",
         depth: 1,
-        link: "/references/workflows/removeFromCartWorkflow"
+        link: "/references/medusa-workflows/deleteLineItemsWorkflow"
       },
       {
         name: "useQueryGraphStep",

www/apps/resources/app/recipes/commerce-automation/page.mdx

@@ -64,7 +64,7 @@ This approach allows you to interact with the third-party service within custom
 
 You can also automate sending notifications to customers when changes happen related to their orders, returns, exchanges, and more.
 
-Medusa's Notification Module allows you to send notifications when an event is triggered, such as when a customer's order is updated. You can use third-party services, like [SendGrid](../../infrastructure-modules/notification/sendgrid), to send emails to customers.
+Medusa's Notification Module allows you to send notifications when an event is triggered, such as when a customer's order is updated. You can use third-party services, like [SendGrid](../../infrastructure-modules/notification/sendgrid/page.mdx), to send emails to customers.
 
 <CardList items={[
   {
@@ -156,7 +156,7 @@ Medusa's commerce features are geared towards automating RMA flows and ensuring
 
 <CardList items={[
   {
-    href: "/commerce-modules/orders",
+    href: "/commerce-modules/order",
     title: "Order Module",
     text: "Learn about the Order Module and its features.",
     icon: AcademicCapSolid,

www/apps/resources/app/recipes/erp/odoo/page.mdx

@@ -572,7 +572,7 @@ You create a step using `createStep` from the Workflows SDK. It accepts two para
 1. The step's name, which is `get-products-from-erp`.
 2. An async function that executes the step's logic. The function receives two parameters:
    - The input data for the step, which are the pagination fields `offset` and `limit`.
-   - An object holding the workflow's context, including the [Medusa Container](!docs!learn/fundamentals/medusa-container) that allows you to resolve Framework and commerce tools.
+   - An object holding the workflow's context, including the [Medusa Container](!docs!/learn/fundamentals/medusa-container) that allows you to resolve Framework and commerce tools.
 
 In this step, you resolve the Odoo Module's service from the container and use its `listProducts` method to fetch products from Odoo. You pass the pagination options from the input data to the method.
 

www/apps/resources/app/recipes/erp/page.mdx

@@ -468,7 +468,7 @@ Then, for each product variant, you use a `canCompanyPurchaseProduct` method in
 
 So, only customers who are allowed in the ERP system to purchase a product can add it to the cart.
 
-Learn more about workflow hooks and how to consume them in [this documentation](/docs/learn/fundamentals/workflows/workflow-hooks).
+Learn more about workflow hooks and how to consume them in [this documentation](!docs!/learn/fundamentals/workflows/workflow-hooks).
 
 ---
 

www/apps/resources/app/recipes/multi-region-store/page.mdx

@@ -34,7 +34,7 @@ During checkout, Medusa calculates the taxes using the tax region settings of th
 
 <CardList items={[
   {
-    href: "!user-guides!/settings/tax-regions",
+    href: "!user-guide!/settings/tax-regions",
     title: "Using Medusa Admin",
     text: "Learn how to manage tax regions in the Medusa Admin",
     icon: UsersSolid,

www/apps/resources/app/recipes/oms/page.mdx

@@ -78,7 +78,7 @@ In addition, you can create a subscriber that listens to fulfillment-related eve
     icon: AcademicCapSolid,
   },
   {
-    href: "/commerce-modules/order/events",
+    href: "/references/order/events",
     title: "Order Events",
     text: "Learn about the events emitted related to the Order Module",
     icon: AcademicCapSolid,
@@ -109,7 +109,7 @@ In addition, you can create a subscriber that listen to payment-related events,
     icon: AcademicCapSolid,
   },
   {
-    href: "/commerce-modules/payment/events",
+    href: "/references/payment/events",
     title: "Payment Events",
     text: "Learn about the events emitted related to the Payment Module",
     icon: AcademicCapSolid,
@@ -175,7 +175,7 @@ Medusa also emits events related to these actions, such as `order.return_request
     icon: AcademicCapSolid,
   },
   {
-    href: "/commerce-modules/order/events",
+    href: "/references/order/events",
     title: "Order Events",
     text: "Learn about the events emitted related to the Order Module",
     icon: AcademicCapSolid,

www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx

@@ -937,7 +937,7 @@ To support subscriptions, you need to support capturing the payment each time th
 
 <Note title="Tip">
 
-If you're using a custom payment provider, you can handle that additional data in the [initiatePayment method](!resources!/references/payment/provider#initiatepayment) of your provider's service.
+If you're using a custom payment provider, you can handle that additional data in the [initiatePayment method](/references/payment/provider#initiatepayment) of your provider's service.
 
 </Note>