Fix bandit hashlib md5

[mlim19]

Resolve CWE-327 https://cwe.mitre.org/data/definitions/327.html

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots

Checklist:

• I have updated the relevant documentation.
• I have added tests for new logic.

[skamerintel]

if this codebase assumes there is no existing data in postgresdb which would have already been hashed with md5, why not address the security concern of md5 being too old by changing the hash function to use hashlib.sha256 rather than keeping md5 and
setting attribute of usedforsecurity=False ?

[mlim19]

if this codebase assumes there is no existing data in postgresdb which would have already been hashed with md5, why not address the security concern of md5 being too old by changing the hash function to use hashlib.sha256 rather than keeping md5 and setting attribute of usedforsecurity=False ?

I thought about switching to sha256 here but users may have existing data which will break compatibility with the change. That's why I keep md5 for now because it's not used for security purpose.

[skamerintel]

ok, approved.

[skamerintel]

approved.