Also include path of file in hash computation.

Followup to 72d3e08067. Without this, the hash wouldn't change and the client
wouldn't reload if a file was renamed in a way that didn't change the order
of files (eg, preserving its name in alphabetical order).

This didn't used to be a problem, as the hash computation was only used in
appcached, which included the file path already and would change if the
file was renamed.

packages/webapp/webapp_server.js

@@ -166,6 +166,7 @@ var calculateClientHash = function () {
   hash.update(JSON.stringify(__meteor_runtime_config__), 'utf8');
   _.each(WebApp.clientProgram.manifest, function (resource) {
     if (resource.where === 'client' || resource.where === 'internal') {
+      hash.update(resource.path);
       hash.update(resource.hash);
     }
   });