Plugins cannot be installed when published under an npm-scope

[olsn]

• [x] I am on the latest Cerebro.app version
• [x] I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Windows 10
• Cerebro.app version: 0.3.2, 0.3.3 / master
• Relevant information from devtools:

Version: 0.1.0
Extract https://registry.npmjs.org/@omm/cerebro-confluence-jira/-/cerebro-confluence-jira-0.1.0.tgz to C:\Users\Olaf\AppData\Roaming\Cerebro\plugins\node_modules\@omm\cerebro-confluence-jira
Download and extract to temp path: C:\Users\Olaf\AppData\Local\Temp/cerebro-confluence-jira
Move C:\Users\Olaf\AppData\Local\Temp/cerebro-confluence-jira to C:\Users\Olaf\AppData\Roaming\Cerebro\plugins\node_modules\@omm\cerebro-confluence-jira
Error in package installation
Error: ENOENT: no such file or directory, rename 'C:\Users\Olaf\AppData\Local\Temp\cerebro-confluence-jira' -> 'C:\Users\Olaf\AppData\Roaming\Cerebro\plugins\node_modules\@omm\cerebro-confluence-jira'

Issue

When a plugin is published under a specific scope (e.g. via an npm-organization), like in my case @omm/cerebro-confluence-jira - the plugin-installation will fail. Dev-tools output is listed above - the installation-process could be probably fixed by replacing the slash in the module-name with something else - but I'm not sure if that might not cause any unwanted sideeffects. For now i've published by plugin without a scope - I've left my other plugin published though in case someone wants to try to reproduce this issue.