fix: escape glob pattern for SASS copy to work in CI

- fixes an issue when trying to publish ms-select-vanilla lib with npm provenance, I found that it was missing some SASS files even though it was working fine locally, it turns out that as pointed out in the `copyfiles` lib, we are better off escaping copyfiles glob patterns in npm scripts
> if your terminal doesn't support globstars then you can quote them

packages/common/package.json

@@ -60,7 +60,7 @@
     "sass-build-task:scss-compile:salesforce-lite": "sass src/styles/slickgrid-theme-salesforce.lite.scss dist/styles/css/slickgrid-theme-salesforce.lite.css --style=compressed --quiet-deps --no-source-map --load-path=node_modules",
     "sass:build": "run-p sass-build-task:scss-compile:*",
     "postsass:build": "postcss --no-map --use cssnano --use autoprefixer --dir dist/styles/css dist/styles/css --style=compressed --quiet-deps --no-source-map",
-    "sass:copy": "cross-env copyfiles -f src/styles/*.scss dist/styles/sass",
+    "sass:copy": "cross-env copyfiles -f \"./src/styles/*.scss\" dist/styles/sass",
     "sass:watch:bootstrap": "npm run sass-build-task:scss-compile:bootstrap -- --watch",
     "sass:watch:material": "npm run sass-build-task:scss-compile:material -- --watch",
     "sass:watch:salesforce": "npm run sass-build-task:scss-compile:salesforce -- --watch",