Modify how 'override' argument is implemented

[end2endzone]

The current implementation defines --override as the following:

• If *.h or *.cpp file exists,
• Compute MD5 of input file and compare with MD5 found in *.cpp file.
• If MD5 compare is the same, skip file generation
• Else, look for the --override flag for deciding if we should regenerate the output file.

This makes the --override flag useless if the MD5 in the cpp file is not changed while the content of the *.cpp file is changed.

In other words, --override should always override the output files

The implementation should be changed as the following:

• By default, the application stores the input file 'modified date' into the generated output files header.
• If the output files exists and that 'modified date' in the generated files matches the intput files, then skip file regeneration (the resulting files will likely be the same which will trigger Visual Studio to rebuild the project)
• If the --override flag is specified, then the application should not look for the 'modified date' value and regenerated the files anyway.

[end2endzone]

Note that implementing this will let the MD5 computation obsolete. The MD5 implementation may be set as deprecated.

The getMd5() api will also be broken.

[end2endzone]

Another option would be to store the input file's modified date into the destination files. This date would allow the application to know if the input file was modified.

The rules are as follow:

• If the override flag is specified, override the destination files.
• If the destination files already exists and that input file is modifed, then the override flag should be automatically set.