v1.10.0: Merge branch 'release/1.10.0'

* release/1.10.0:
  FIX: Update Node-Sass; Use same versioning for Dev and Prod
  FIX: Release Candidates must be PRs to master
  NEW: Bump to v1.9.0
  IMPROVE: Use clearer pre-release labels in SemVer versions
  IMPROVE: Include content in Source Maps

1.9.1 Release Candidates use `rc.[build]`

The pre-release label for Release Candidates has been amended to produce the label as rc.[build] rather than rc[build]

Clearer pre-release labels in our SemVer-ish versions

• Development builds do not include the version or a pre-release
  specifier no matter which branch is used.

  This reliably produces a local artifact with the filename CEC.war
  that Developers can sync without accouting for changes in the version
  #.

• Production builds include the version number, from package.json,
  and a pre-release specifier.

  • master produces the artifact named CEC-[VERSION].

  • release/ and hotfix/ branches produce an artifact named CEC-[VERSION]-rc[BUILD]:

    • [VERSION] is the version from package.json.
    • [BUILD] is the incremental build # from the CI.

  • feature/ branches produce an artifact named CEC-[VERSION]-[BRANCH].[BUILD].[COMMIT_ID]:

    • [VERSION] is the version from package.json.
    • [BUILD] is the incremental build # from the CI.
    • [COMMIT_ID] is the short commit id. This should provide
      a small measure of convenience when troubleshooting.

Updated Web Manifest

Builds now include a Java Web Manifest with the build metadata that indicates the artifact's provenance (Branch, Author, Commit ID etc).

1.7.0

• Include Jenkins Build # in archive filename
  Appends the Jenkins Build Number to the development archive name.
  New archive name: CEC-{VERSION}-BUILD-{BUILD_NUMBER}

  For local builds, if the environment variable "BUILD_NUMBER" is not available, the -{BUILD_NUMBER} suffix is not appended.

• Include a JSON version manifest as part of the build in version.json. It contains the version that was built, the commit hash and the build date.