feat: release to npm after user defined plugins (#105)

* feat: release to npm after creating git commit

With `@semantic-release/npm` being used before `@semantic-release/git` the NPM release doesn't contain updated `CHANGELOG.md` and `package.json`.
And that can be very confusing for the consumers of the package.

Simply changing the order of plugins should fix that. GitHub plugin already is in that order, so it will be consistent.

* put both npm and github before git plugin

Author: Balvajs

packages/nx-semantic-release/src/executors/semantic-release/plugins.ts

@@ -84,10 +84,17 @@ export const resolvePlugins = (
           ],
         ]
       : emptyArray),
-    ...(options.npm ? getNpmPlugin(context, options) : emptyArray),
     ...(options.plugins ?? []),
   ];
 
+  if (options.npm) {
+    defaultPlugins.push(...getNpmPlugin(context, options));
+  }
+
+  if (options.github) {
+    defaultPlugins.push(['@semantic-release/github', options.githubOptions]);
+  }
+
   if (options.git) {
     defaultPlugins.push([
       '@semantic-release/git',
@@ -109,9 +116,5 @@ export const resolvePlugins = (
     ]);
   }
 
-  if (options.github) {
-    defaultPlugins.push(['@semantic-release/github', options.githubOptions]);
-  }
-
   return defaultPlugins;
 };