docs(serverConfig): Remove server config option from TOML

.changesets/11176.md

@@ -1,5 +1,6 @@
 - fix(api-server): Use createServer in all cases, to make fastify config consistent (#11176) by @dac09
 
-This PR removes all the cases where we use `createFastifyInstance` for the api server, and replaces it with `createServer`.
+[BREAKING] Removes serverConfig support, in favour of server file to configure your Fastify instance.
+You can still customise your server settings by running `yarn rw setup server-file` first. See docs for [Server File](https://docs.redwoodjs.com/docs/docker/#using-the-server-file)
 
-This makes sure that the API server config is always consistent - whether you use a server file or not. (createServer was only used when we had a server file before)
+This PR removes all the cases where we use `createFastifyInstance` for the api server, and replaces it with `createServer`. This makes sure that the API server config is always consistent - whether you use a server file or not.

docs/docs/app-configuration-redwood-toml.md

@@ -111,7 +111,10 @@ Don't make secrets available to your web side. Everything in `includeEnvironment
 | `host`         | Hostname for the api server to listen at               | Defaults to `'0.0.0.0'` in production and `'::'` in development              |
 | `schemaPath`   |  The location of your Prisma schema. If you have [enabled Prisma multi file schemas](https://www.prisma.io/docs/orm/prisma-schema/overview/location#multi-file-prisma-schema), then its value is the directory where your `schema.prisma` can be found, for example: `'./api/db/schema'` | Defaults to `'./api/db/schema.prisma'` |
 | `debugPort`    | Port for the debugger to listen at     | `18911`                    |
-| `serverConfig` | [Deprecated; use the [server file](./docker.md#using-the-server-file) instead] Path to the `server.config.js` file | `'./api/server.config.js'` |
+
+
+Additional server configuration can be done using [Server File](docker.md#using-the-server-file)
+
 
 ### Multi File Schema