fix: switch to SHA1 and add a try/catch block on acl inheritance hashing

[rvazarkar]

Description

MD5 hashing is not FIPS compliant and in environments where compliance is enforced, .net will throw an exception. Switching to SHA1 will solve this issue. Additional try/catch for safety added.

Motivation and Context

https://specterops.atlassian.net/browse/BP-988

How Has This Been Tested?

Tested in GOAD w/ FIPS enforcement enabled

Screenshots (if appropriate):

Types of changes

• [ ] Chore (a change that does not modify the application functionality)
• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [ ] Documentation updates are needed, and have been made accordingly.
• [ ] I have added and/or updated tests to cover my changes.
• [x] All new and existing tests passed.
• [ ] My changes include a database migration.