docs: shorten npx commands (#4652)

docs/content/development/entities/create.md

@@ -123,7 +123,7 @@ npm run build
 Then, run the `migration` command:
 
 ```bash
-npx @medusajs/medusa-cli migrations run
+npx medusa migrations run
 ```
 
 You should see that your migration have executed.

docs/content/development/entities/extend-entity.md

@@ -109,7 +109,7 @@ npm run build
 Then, run the following command to migrate your changes to the database:
 
 ```bash
-npx @medusajs/medusa-cli migrations run
+npx medusa migrations run
 ```
 
 You should see that your migration was executed, which means your changes were reflected in the database schema.

docs/content/development/entities/extend-repository.md

@@ -125,7 +125,7 @@ npm run build
 Then, run the following command to start your backend:
 
 ```bash npm2yarn
-npx @medusajs/medusa-cli develop
+npx medusa develop
 ```
 
 You should see your custom implementation working as expected.

docs/content/development/entities/migrations/create.md

@@ -90,7 +90,7 @@ npm run build
 The last step is to run the migration with the command detailed earlier
 
 ```bash
-npx @medusajs/medusa-cli migrations run
+npx medusa migrations run
 ```
 
 If you check your database now you should see that the change defined by the migration has been applied successfully.

docs/content/development/entities/migrations/overview.mdx

@@ -32,7 +32,7 @@ Migrations are used to apply changes to the database schema. However, there are
 Using the Medusa CLI tool, you can run migrations with the following command:
 
 ```bash
-npx @medusajs/medusa-cli migrations run
+npx medusa migrations run
 ```
 
 This will check for any migrations that contain changes to your database schema that aren't applied yet and run them on your backend.