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/integrations/guides/magento/page.mdx

@@ -763,7 +763,7 @@ You create a step using `createStep` from the Workflows SDK. It accepts two para
 1. The step's name, which is `get-magento-products`.
 1. An async function that executes the step's logic. The function receives two parameters:
    - The input data for the step, which in this case is the pagination parameters.
-   - 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 the step function, you resolve the Magento Module's service from the container, then use its `getProducts` method to retrieve the products from Magento.
 

www/apps/resources/app/integrations/guides/sanity/page.mdx

@@ -1664,7 +1664,7 @@ To render a widget that matches the rest of the admin dashboard's design, you us
 
 <Note>
 
-Learn more about widgets in [this documentation](/learn/fundamentals/admin/widgets).
+Refer to the [Admin Widgets](!docs!/learn/fundamentals/admin/widgets) documentation to learn more.
 
 </Note>
 
@@ -1746,7 +1746,7 @@ export const POST = async (req: MedusaRequest, res: MedusaResponse) => {
 
 This adds a `POST` API route at `/admin/sanity/syncs`. In the route handler, you execute the `sanitySyncProductsWorkflow` without passing it a `product_ids` input. The step in the workflow will retrieve all products, instead of filtering them by ID, and sync them to Sanity.
 
-You return the transaction ID of the workflow, which you can use to track the execution's progress since the workflow will run in the background. This is not implemented in this guide, but Medusa has a [Get Execution API route](!api!admin#workflows-executions_getworkflowsexecutionsworkflow_idtransaction_id) that you can use to get the details of a workflow's execution.
+You return the transaction ID of the workflow, which you can use to track the execution's progress since the workflow will run in the background. This is not implemented in this guide, but Medusa has a [Get Execution API route](!api!/admin#workflows-executions_getworkflowsexecutionsworkflow_idtransaction_id) that you can use to get the details of a workflow's execution.
 
 ### Add Sanity UI Route
 

www/apps/resources/app/integrations/page.mdx

@@ -27,7 +27,7 @@ An Analytics Module Provider tracks events and user behavior in your Medusa appl
       title: "PostHog"
     },
     {
-      href: "/infrastructure-modules/analytics/segment",
+      href: "/integrations/guides/segment",
       title: "Segment",
       badge: {
         variant: "blue",