fix(publish): fix publish adding an additional '@'

Changes in @salesforce/command has led to ignoring the removal of '@' symbol added by a user during
the parsing of the flag. This has led subsequent code to add '@' again, as '@' is mandatory for
scopde package and users may ignore adding '@' to the scope. This was clearly the established
behaviour with publish command. This fix reintroduces previous behaviours

issue not created in github, but refered in slack as
https://dxatscale.slack.com/archives/CN9N54GF5/p1670321226990929

Author: azlam-abdulsalam

packages/sfpowerscripts-cli/package-lock.json

@@ -1,7 +1,7 @@
 {
     "name": "@dxatscale/sfpowerscripts",
     "description": "DX@Scale Toolkit",
-    "version": "20.2.5",
+    "version": "20.2.6",
     "author": "dxatscale",
     "release": "November 22",
     "bin": {

packages/sfpowerscripts-cli/package.json

@@ -281,7 +281,12 @@ export default class Promote extends SfpowerscriptsCommand {
         // NPM does not accept packages with uppercase characters
         let name: string = sfpPackage.packageName.toLowerCase() + '_sfpowerscripts_artifact';
 
-        if (this.flags.scope) name = `@${this.flags.scope.toLowerCase()}/` + name;
+        //Check whether the user has already passed in @
+
+        if (this.flags.scope) {
+            let scope: string = this.flags.scope.replace(/@/g, '').toLowerCase();
+            name = `@${scope}/` + name;
+        }
 
         let packageJson = {
             name: name,