Enable build/test/publish pipeline for Platform Server

[MikeTheCanuck]

There will be a special Docker container deploy (or simple EC2 VM) to host the Node.js server that hosts all the projects' frontend NPM packages.

This will have to include a design decision (to be negotiated with @DavideDaniel) on how specifically to signal to the Platform Server repo that a frontend project has successfully published a new NPM package version. Ideas discussed included various combinations of things like:

• Project submits PR to Platform Server repo that increments a project-specific file, causing a new build of the Platform Server
• Project makes commit to Platform Server repo to increment a version number in package.json for their specific Project's package

Platform Server shouldn't need to worry about binding to specific version of Project's package - "[package]:latest" should be sufficient, assuming that each frontend Project is able to eventually implement build tests that ensure the package will install successfully and won't taken down the Platform Server (whatever "take down" means in this context).

[MikeTheCanuck]

This architectural feature has been mooted - at the last Platform team meeting (2017-10-22), it was announced that there are no further plans to use a front-end Node.js server, but rather to run all frontend code in the browser.