Fix BinSkim errors

[jessamp]

Hi, I have a request to fix the BinSkim errors with hermes. Looks like you'll need to change build flags to disable MD5 hashing and re-enable warnings 4146;4244;4267. When I run the task in our build pipeline, here's what binskim is showing us:

`hermes.dll: error BA2004: 'hermes.dll' is a native binary that directly compiles and links one or more object files which were hashed using an insecure checksum algorithm (MD5). MD5 is subject to collision attacks and its use can compromise supply chain integrity. Pass '/ZH:SHA_256' on the cl.exe command-line to enable secure source code hashing.

hermes.dll: error BA2007: 'hermes.dll' disables compiler warning(s) which are required by policy. A compiler warning is typically required if it has a high likelihood of flagging memory corruption, information disclosure, or double-free vulnerabilities. To resolve this issue, enable the indicated warning(s)`

[mganandraj]

Hi @jessamp, do you still need this to be looked at ?

[jessamp]

@mganandraj yes. We've worked around this by ignoring this error for now, but would prefer if the errors were fixed. Thanks!

[mganandraj]

Tudor checked in the following fix a while back to fix the object file checksum.
bcda87c

but the compiler warnings are yet to be enabled.

[slobo80]

We also need this fix. Please prioritize if you can.