CSS modules are not correctly hashed #325
Description
Bug
It appears that the hashes for CSS modules are not calculated based on content hash, they are instead based upon the file path, which means that if 2 applications are placed on the same page with the same file structure the hashes can collide.
We should add an additional part to the existing hash that at least adds some kind of project level uniqueness, we have that currently in the form of the libraryName (which is based on the package.json name) which we use elsewhere.