feat: update docs where create-plugin is used with new --select plugin

Signed-off-by: Sayak Mukhopadhyay <mukhopadhyaysayak@gmail.com>

docs/plugins/backend-plugin.md

@@ -28,7 +28,7 @@ lowercase characters separated by dashes, for example `carmen`, if it's a
 package that adds an integration with a system named Carmen, for example. The
 full NPM package name would then be something like
 `@internal/plugin-carmen-backend`, depending on the other flags passed to the
-`create-plugin` command, and your settings for the `create-plugin` command in
+`new` command, and your settings for the `new` command in
 your root `package.json`.
 
 Creating the plugin will take a little while, so be patient. It will helpfully

docs/plugins/create-a-plugin.md

@@ -11,13 +11,14 @@ A Backstage Plugin adds functionality to Backstage.
 To create a new plugin, make sure you've run `yarn install` and installed
 dependencies, then run the following on your command line (a shortcut to
 invoking the
-[`backstage-cli create-plugin`](../local-dev/cli-commands.md#create-plugin))
+[`backstage-cli new --select plugin`](../local-dev/cli-commands.md#new))
 from the root of your project.
 
 ```bash
 yarn new --select plugin
 ```
 
+// Todo: change the asses to show the output of the new command
 ![](../assets/getting-started/create-plugin_output.png)
 
 This will create a new Backstage Plugin based on the ID that was provided. It

docs/plugins/integrating-plugin-into-software-catalog.md

@@ -21,7 +21,7 @@ should have a separate package in a folder, which represents your plugin.
 Example:
 
 ```
-$ yarn create-plugin
+$ yarn new --select plugin
 > ? Enter an ID for the plugin [required] my-plugin
 > ? Enter the owner(s) of the plugin. If specified, this will be added to CODEOWNERS for the plugin path. [optional]