Publish dev versions of all core artefacts to npm using fluid-publish

Details

Description

Rather than gearing dependencies using git hashes, it is time to migrate to the use of npm in order to resolve and distribute artefacts. This will make it easier to track the components of deployed builds as well as show these in logs and UI in issues such as GPII-2215, GPII-2216.

This will need a wholesale rename of all of our npm artefacts in package.json and require statements - e.g. universal -> gpii-universal, windows -> gpii-windows etc. It may also require us to tweak some directory names in build scripts - a final possibility is that we might need to rename the git repositories themselves, although this last should be a last resort since it will invalidate everyone's checkouts.

We will initially use the https://www.npmjs.com/package/fluid-publish tool to publish dev artefacts, but this is a necessary stepping stone to moving the GPII over to an official release process with QAed and checked artefacts with proper semver numbers.