Fix Webpack cache invalidation

[malash]

The Webpack cache should be invalidated if:

1. The build target has changed, i.e., when using yarn start [target].
2. The GojiJS version has changed, typically after updating the GojiJS CLI.
3. There has been a change in the webpack.config.js. This recommendation is provided in the Webpack cache configuration documentation. Additionally, this has been implemented in Webpack CLI.
4. There is a change in the goji.config.js. This is crucial because users often modify goji.config.js to adjust the build configuration.