fix: handle correctly the situation when the compilation hash is the same as the previous one

Currently CLI considers the hash that is the same as the previous as invalid and this way the application is restarted on device. As that hash is already handled, we should consider it as a valid hash.
Steps to reproduce :
```
`tns create ts_proj`  - choose ts tabs project

npm i tns-core-modules@rc --save --save-exact

npm i nativescript-dev-webpack@rc --save-dev --save-exact

node_modules/.bin/update-ns-webpack --deps –configs

tns run android

Change something in app.android.scss - the change is applied, no restart

Change something in app.ios.scss - application restarts
```

Author: Fatme

lib/services/webpack/webpack-compiler-service.ts

@@ -46,6 +46,11 @@ export class WebpackCompilerService extends EventEmitter implements IWebpackComp
 							return;
 						}
 
+						// the hash of the compilation is the same as the previous one
+						if (this.expectedHashes[platformData.platformNameLowerCase] === message.hash) {
+							return;
+						}
+
 						let result;
 
 						if (prepareData.hmr) {