Remove Railpack-related prerequisites from Railway deployment documentation (#3181)

Co-authored-by: cprecioso <[email protected]>
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: Carlos Precioso <[email protected]>

Author: Copilot

web/docs/deployment/deployment-methods/paas.md

@@ -232,7 +232,6 @@ To get started, follow these steps:
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account.
 1. Install the [Railway CLI](https://docs.railway.com/develop/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli).
 1. Run `railway login` and a browser tab will open to authenticate you.
-1. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable **Railpack** as the default deployment builder. This is required for the client routing to work correctly.
 
 ### Create New Project
 
@@ -332,7 +331,7 @@ You'll deploy the server first:
 
     Select `client` when prompted to select a service.
 
-    Railway will detect the `index.html` file and deploy the client as a static site using [Railpack](https://railpack.com/languages/staticfile#root-directory-resolution).
+    Railway will detect the `index.html` file and deploy the client as a static site.
 
 
 And now your Wasp should be deployed!

web/docs/deployment/deployment-methods/wasp-deploy/railway.md

@@ -14,8 +14,6 @@ To deploy to Railway using Wasp CLI:
 
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account,
 
-1. Wasp CLI requires that Railpack is set as the default deployment builder **for client routing to work correctly**. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable "Default to Railpack".
-
 1. Install the [`railway` CLI](https://docs.railway.com/guides/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli) on your machine.
 
 ## Deploying

web/versioned_docs/version-0.17.0/deployment/deployment-methods/paas.md

@@ -229,7 +229,6 @@ To get started, follow these steps:
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account.
 1. Install the [Railway CLI](https://docs.railway.com/develop/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli).
 1. Run `railway login` and a browser tab will open to authenticate you.
-1. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable **Railpack** as the default deployment builder. This is required for the client routing to work correctly.
 
 ### Create New Project
 
@@ -330,7 +329,7 @@ You'll deploy the server first:
 
     Select `client` when prompted to select a service.
 
-    Railway will detect the `index.html` file and deploy the client as a static site using [Railpack](https://railpack.com/languages/staticfile#root-directory-resolution).
+    Railway will detect the `index.html` file and deploy the client as a static site.
 
 
 And now your Wasp should be deployed!

web/versioned_docs/version-0.17.0/deployment/deployment-methods/wasp-deploy/railway.md

@@ -14,8 +14,6 @@ To deploy to Railway using Wasp CLI:
 
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account,
 
-1. Wasp CLI requires that Railpack is set as the default deployment builder **for client routing to work correctly**. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable "Default to Railpack".
-
 1. Install the [`railway` CLI](https://docs.railway.com/guides/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli) on your machine.
 
 ## Deploying

web/versioned_docs/version-0.18.0/deployment/deployment-methods/paas.md

@@ -232,7 +232,6 @@ To get started, follow these steps:
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account.
 1. Install the [Railway CLI](https://docs.railway.com/develop/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli).
 1. Run `railway login` and a browser tab will open to authenticate you.
-1. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable **Railpack** as the default deployment builder. This is required for the client routing to work correctly.
 
 ### Create New Project
 
@@ -332,7 +331,7 @@ You'll deploy the server first:
 
     Select `client` when prompted to select a service.
 
-    Railway will detect the `index.html` file and deploy the client as a static site using [Railpack](https://railpack.com/languages/staticfile#root-directory-resolution).
+    Railway will detect the `index.html` file and deploy the client as a static site.
 
 
 And now your Wasp should be deployed!

web/versioned_docs/version-0.18.0/deployment/deployment-methods/wasp-deploy/railway.md

@@ -14,8 +14,6 @@ To deploy to Railway using Wasp CLI:
 
 1. Create a [Railway](https://railway.com/?utm_medium=integration&utm_source=docs&utm_campaign=wasp) account,
 
-1. Wasp CLI requires that Railpack is set as the default deployment builder **for client routing to work correctly**. Go to your [Railway account settings](https://railway.com/account/feature-flags?utm_medium=integration&utm_source=docs&utm_campaign=wasp) and enable "Default to Railpack".
-
 1. Install the [`railway` CLI](https://docs.railway.com/guides/cli?utm_medium=integration&utm_source=docs&utm_campaign=wasp#installing-the-cli) on your machine.
 
 ## Deploying