docs(pdk-migration): update guide for @aws/nx-plugin 1.0.0-rc.33

- Bump the pinned version from 1.0.0-rc.10 to 1.0.0-rc.33
- Drop the manual tsx install step: ts#smithy-api vends tsx as a dev
  dependency since #786
- Rename the serve-local target to dev following #806
- Pass ux=cloudscape to ts#website since the default changed to shadcn
  in #854 (the shopping list app uses CloudScape components)
- Fix the vite.config.mts outDir shown in the ace-builds diff context
  to match the generated config (bundle subdirectory)

Validated by running the full migration end-to-end on a fresh
1.0.0-rc.33 workspace, including a live AWS deploy, authenticated
GET/POST/DELETE API tests and teardown.

Author: test

docs/src/content/docs/en/blog/migrating-from-aws-pdk.mdx

@@ -36,7 +36,7 @@ Note also that some features of PDK don't have exact equivalents. Refer to the [
 :::
 
 :::caution[Point-in-Time Guide]
-This is written as a point-of-time guide and will most likely not be updated as the Nx Plugin for AWS evolves. To compensate for this, the guide pins the version of `@aws/nx-plugin` to `1.0.0-rc.10`. You can try with the latest version if following along, but there may be some deviations from the guide.
+This is written as a point-of-time guide and will most likely not be updated as the Nx Plugin for AWS evolves. To compensate for this, the guide pins the version of `@aws/nx-plugin` to `1.0.0-rc.33`. You can try with the latest version if following along, but there may be some deviations from the guide.
 :::
 
 ## Example Migration: Shopping List Application
@@ -54,7 +54,7 @@ The shopping list application consists of the following PDK project types:
 
 To start, we'll create a new workspace for our new project. While more extreme than an in-place migration, this approach gives us the cleanest end result. Creating an Nx workspace is equivalent to using PDK's `MonorepoTsProject`:
 
-<CreateNxWorkspaceCommand workspace="shopping-list" iac="cdk" tag="1.0.0-rc.10" />
+<CreateNxWorkspaceCommand workspace="shopping-list" iac="cdk" tag="1.0.0-rc.33" />
 
 Open up the `shopping-list` directory this command creates in your favourite IDE.
 

docs/src/content/docs/en/snippets/pdk-migration/example/02-migrate-website.mdx

@@ -17,9 +17,9 @@ As part of the migration, we will also move from PDK's configured React Router t
 
 #### Generate a React Website
 
-Run the <Link path="/guides/react-website">`ts#website` generator</Link> with `framework` set to `react` to set up your website project in `packages/website`:
+Run the <Link path="/guides/react-website">`ts#website` generator</Link> with `framework` set to `react` to set up your website project in `packages/website`. Since the shopping list application is built with CloudScape components, we also set `ux` to `cloudscape` (the default is `shadcn`):
 
-<RunGenerator generator="ts#website" noInteractive requiredParameters={{ name: 'website', framework: 'react' }} />
+<RunGenerator generator="ts#website" noInteractive requiredParameters={{ name: 'website', framework: 'react', ux: 'cloudscape' }} />
 
 #### Add Cognito Authentication
 
@@ -66,7 +66,7 @@ The `CloudscapeReactTsWebsiteProject` automatically included a dependency on `@a
 ```diff lang="ts"
 // packages/website/vite.config.mts
   build: {
-    outDir: '../../dist/packages/website',
+    outDir: '../../dist/packages/website/bundle',
     emptyOutDir: true,
     reportCompressedSize: true,
     commonjsOptions: {
@@ -98,16 +98,12 @@ Note that you'll now have some build errors visible in your IDE, we'll need to m
 
 Since we're using [file-based routing](https://tanstack.com/router/latest/docs/framework/react/routing/file-based-routing), we can use the website local development server to manage automatically generating route configuration.
 
-The Smithy API's local server runs with [`tsx`](https://github.com/privatenumber/tsx), so let's add it as a development dependency before starting the local servers:
+Let's start the local website server:
 
-<InstallCommand dev pkg="tsx" />
-
-Now let's start the local website server:
-
-<NxCommands commands={["serve-local website"]} />
+<NxCommands commands={["dev website"]} />
 
 :::tip
-We're using the `serve-local` target here, which also starts local servers for any APIs which have been connected with `connection`, and hot-reloads if your website, model, or backend changes! This allows us to test our API and website locally before we've even written any CDK code.
+We're using the `dev` target here, which also starts local servers for any APIs which have been connected with `connection`, and hot-reloads if your website, model, or backend changes! This allows us to test our API and website locally before we've even written any CDK code.
 :::
 
 You'll see some errors, but the local website server should start on port `4200`, as well as the local Smithy API server on port `3001`.