docs: used the NPX CLI tool across docs (#4099)

docs/content/plugins/analytics/segment.md

@@ -130,7 +130,7 @@ const plugins = [
 Run your backend with the following command:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 Then, try triggering one of the [mentioned events earlier in this document](#events-that-the-segment-plugin-tracks). For example, you can place an order either using the [REST APIs](https://docs.medusajs.com/api/store) or using the [Next.js starter storefront](../../starters/nextjs-medusa-starter.mdx).

docs/content/plugins/cms/contentful/customize-contentful.md

@@ -251,7 +251,7 @@ export const query = graphql`
 To test this out, run your Medusa backend by running this command in its directory:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 Then run the Gatsby storefront by running this command in its directory:

docs/content/plugins/cms/contentful/index.md

@@ -167,7 +167,7 @@ npm run seed
 To start the backend run the following command:
 
 ```bash
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 If you seeded the database with demo data, you should see that events related to the products are triggered.

docs/content/plugins/cms/strapi.md

@@ -172,7 +172,7 @@ npm run develop
 Then, in the directory of your Medusa backend, run the following command to start the Medusa backend:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 Once you start your Medusa backend, if you ran the `--seed` command when you created your Medusa backend, you’ll see that `product.created` events have been triggered along with similar events. This will update Strapi with the products you seeded.

docs/content/plugins/file-service/s3.md

@@ -177,7 +177,7 @@ If you have multiple storage plugins configured, the last plugin declared in the
 Run your Medusa backend with the following command:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 Then, you can either test the plugin using the [REST APIs](/api/store) or using the [Medusa Admin](../../admin/quickstart.mdx).

docs/content/plugins/file-service/spaces.md

@@ -137,7 +137,7 @@ If you have multiple storage plugins configured, the last plugin declared in the
 Run your Medusa backend with the following command:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 Then, you can either test the plugin using the [REST APIs](/api/store) or using the [Medusa Admin](../../admin/quickstart.mdx).

docs/content/plugins/notifications/sendgrid.mdx

@@ -3962,7 +3962,7 @@ You can also optionally pass the option `localization` if you want to support di
 Run your backend now:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 To test it out, perform an action that would trigger one of the emails being sent. For example, you can use your Medusa storefront to create an order. An email from your SendGrid account will be sent to the customer email.

docs/content/plugins/search/algolia.md

@@ -194,7 +194,7 @@ const plugins = [
 Run your Medusa backend with the following command:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 The quickest way to test that the integration is working is by sending a `POST` request to `/store/products/search`. This endpoint accepts a `q` body parameter of the query to search for and returns in the result the products that match this query.

docs/content/plugins/search/meilisearch.md

@@ -161,7 +161,7 @@ Make sure your MeiliSearch instance is running. If you’re unsure how to run it
 Then, run the Medusa backend:
 
 ```bash npm2yarn
-npm run start
+npx @medusajs/medusa-cli develop
 ```
 
 The quickest way to test that the integration is working is by sending a `POST` request to `/store/products/search`. This endpoint accepts a `q` body parameter of the query to search for and returns in the result the products that match this query.