Remove the limitation on npm package name being identical to project name

Currently we enforce the limitation on the package naming to be identical to that of the project name.

One of the use cases is caching of several thirdparty npm packages related to a single project an in this case it is not doable.

I propose removing this limitation and allowing every project repository to have arbitrary package naming.