feat: add support for scoped packages

[jeetiss]

re #436

• added question about package access on setup step
• added isScopedPackage verification on setup step
• added custom publishCommand to config, based on information from previous step

PS: I added restricted access except scoped package support, if somebody with default package (not scoped) chose don't publish public package. Setup script will add custom publishCommand with --access restricted 🤖

[eunjae-lee]

Hi @jeetiss, thanks for coming up with this PR :)

I've checked the NPM documentation, and found this

[--access <public|restricted>] Tells the registry whether this package should be published as public or restricted. Only applies to scoped packages, which default to restricted. If you don’t have a paid account, you must publish with --access public to publish scoped packages.

I guess un-scoped packages are always published in public. --access should be a thing for only scoped packages.
If I understand correctly, the xor part can be simplified, checking only if it's a scoped package.
What do you think?

[jeetiss]

Yes, @eunjae-lee you right

I'm missed that access flag applies only to scoped packages

[eunjae-lee]

@jeetiss That way, the publishCommand function is being quoted.
What do you think of using https://github.com/yahoo/serialize-javascript instead of JSON.stringify?