feat: modify local development under the hood docs

to reflect the `tsx` refactoring

Author: FilipPyrek

docs/src/content/docs/core-concepts/local-development.mdx

@@ -108,15 +108,14 @@ There are a couple of controls you can use during live local development.
 ## How it works under the hood
 
 - The CLI...
-  1. creates a directory in your system's temp folder
-  2. copies your project files to the temp folder
-  3. watches for any changes in your project and copies the changes to the temp folder
-  4. starts the TypeScript compiler in watch mode to compile the project to JS
-  5. dynamically imports the CDK project file and searches for an exported variable which is of the type `cdk.App`
-  6. searches the stacks to find Buttonize CDK resources
-  7. extracts the Buttonize resources
-  8. tries to fetch the stack metadata and resources from AWS, if the stack has been deployed
-  9. puts everything together and waits for the local connection from [app.buttonize.io/live](https://app.buttonize.io/live)
+
+  1. uses [`tsx`](https://github.com/privatenumber/tsx?tab=readme-ov-file#nodejs-loader) ESM [module loader](https://nodejs.org/api/module.html#customization-hooks) to dynamically import your TypeScript CDK code
+  2. watches for any changes in `.ts, .tsx, .json` files in your project
+  3. searches in the `<entrypoint>` file for an exported variable of the type `cdk.App`
+  4. extracts the Buttonize resources from stacks in the `cdk.App`
+  5. tries to fetch the stack metadata and resources from AWS, if the stack has been deployed
+  6. puts everything together and waits for the local connection from [app.buttonize.io/live](https://app.buttonize.io/live)
+
 - Buttonize Live Local Development UI...
   1. tries to connect to the local dev server
   2. pulls the data and watches for any changes