Improve the --force flag on the php hyde publish:homepage command

[caendesilva]

Right now you always need to supply the --force flag on the php hyde publish:homepage command, even on new installations.

This is a bit jarring and could be improved using the principle of least astonishment. The reason the force flag is there to protect against accidental overrides, however it does not really matter if you override a default page. I suggest we start keeping a JSON cache of default file hashes. When running the publish command, we compare the hash of the current file. If it matches any of the default files we can force the publish. Otherwise, we add a notice to let the user know why their file was not published, and that they can use --force.

[caendesilva]

Dev branch: https://github.com/hydephp/framework/tree/internal-intelligence-refactor

[caendesilva]

Companion branch: https://github.com/hydephp/hyde/tree/iir-companion

[caendesilva]

Fixed in upcoming PR