docs: rename Architectural Modules to Infrastructure Modules (#12212)

* docs: rename Architectural Modules to Infrastructure Modules

* generate again

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

@@ -690,7 +690,7 @@ Since you export a `POST` route handler function, you expose an `API` route at `
 1. A request object with details and context on the request, such as body parameters or authenticated user details.
 2. A response object to manipulate and send the response.
 
-In the route handler, you use the Medusa container that is available in the request object to resolve the [Event Module](../../../architectural-modules/event/page.mdx). This module manages events and their subscribers.
+In the route handler, you use the Medusa container that is available in the request object to resolve the [Event Module](../../../infrastructure-modules/event/page.mdx). This module manages events and their subscribers.
 
 Then, you emit the `algolia.sync` event using the Event Module's `emit` method, passing it the event name.
 

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

@@ -646,7 +646,7 @@ Where:
 
 <Note title="Tip">
 
-Medusa supports integrating third-party services, such as [S3](../../../architectural-modules/file/s3/page.mdx), in a File Module Provider. Refer to the [File Module](../../../architectural-modules/file/page.mdx) documentation to find other module providers and how to create a custom provider.
+Medusa supports integrating third-party services, such as [S3](../../../infrastructure-modules/file/s3/page.mdx), in a File Module Provider. Refer to the [File Module](../../../infrastructure-modules/file/page.mdx) documentation to find other module providers and how to create a custom provider.
 
 </Note>
 

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

@@ -1684,9 +1684,9 @@ Earlier in this guide when introducing workflows, you learned that you can track
 
 ### Retrieve Sync Executions API Route
 
-Medusa has a [workflow engine](../../../architectural-modules/workflow-engine/page.mdx) that manages workflow executions, roll-backs, and other functionalities under the hood.
+Medusa has a [workflow engine](../../../infrastructure-modules/workflow-engine/page.mdx) that manages workflow executions, roll-backs, and other functionalities under the hood.
 
-The workflow engine is an [architectural module](!docs!/learn/fundamentals/modules/architectural-modules), which can be replaced with a [Redis Workflow Engine](../../../architectural-modules/workflow-engine/redis/page.mdx), or a custom one of your choice, allowing you to take ownership of your application's tooling.
+The workflow engine is an [Infrastructure Module](!docs!/learn/fundamentals/modules/infrastructure-modules), which can be replaced with a [Redis Workflow Engine](../../../infrastructure-modules/workflow-engine/redis/page.mdx), or a custom one of your choice, allowing you to take ownership of your application's tooling.
 
 In your customizations, you can resolve the workflow engine from the container and manage executions of a workflow, such as retrieve them and check their progress.
 

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

@@ -91,7 +91,7 @@ A File Module Provider uploads and manages assets, such as product images, on a
 <CardList
   items={[
     {
-      href: "/architectural-modules/file/s3",
+      href: "/infrastructure-modules/file/s3",
       title: "AWS S3 (and Compatible APIs)"
     }
   ]}
@@ -131,7 +131,7 @@ A Notification Module Provider sends messages to users and customers in your Med
 <CardList
   items={[
     {
-      href: "/architectural-modules/notification/sendgrid",
+      href: "/infrastructure-modules/notification/sendgrid",
       title: "SendGrid"
     },
     {