ID 551242 - An error occurs if a Cryptomatte node's sidecar manifest is empty or contains custom hashes

Problem summary:
An error occurs if a Cryptomatte node's sidecar manifest is empty or contains custom hashes
 
Customer reported version:
Nuke 13.2v7
 
Customer reported platform:
CentOS 7
 
Steps to reproduce:
1) Create or download an .exr with a sidecar manifest, such as this bunny_CryptoObject.exr from Psyop.
2) Create an empty file in the same directory as the .exr named "bunny_CryptoObject_manifest.json".
3) Launch Nuke, and create a Read node in the Node Graph.
4) Select the bunny_CryptoObject.exr file, and then create a Cryptomatte node.
5) View the Cryptomatte and observe the error message: Cryptomatte1: "/path/to/the/bunny_CryptoObject_manifest.json" is not a valid sidecar manifest file path

 
Expected behavior:
Nuke's Cryptomatte node should behave like Psyop's Cryptomatte node, and not raise errors with empty sidecar manifests or sidecar manifests with custom hashing.
 
Actual behavior:
Cryptomatte nodes that point to empty manifest files or manifests with custom hashing will produce a "'<manifest path>' is not a valid sidecar manifest file path" error.
 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke 14.0v5 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 13.0v1 - The native Cryptomatte node did not exist before this version