Upgrade xml-crypto dependency

[mans0954]

• Bump xml-crypto from 1.4.0 to 1.5.3
• Include package-lock.json in repo

May possibly help with #456 ?

[cjbarth]

@mans0954 , how would this help with #456? It seems that #465 is reporting that moving to v1.5.3 is what caused the problem in the first place. Unfortunately neither @yj188 nor @Harsha3878 provided a clear reproduction or a test that can be used to figure out what is going on.

[mans0954]

@mans0954 , how would this help with #456? It seems that #465 is reporting that moving to v1.5.3 is what caused the problem in the first place. Unfortunately neither @yj188 nor @Harsha3878 provided a clear reproduction or a test that can be used to figure out what is going on.

The test pass with v1.5.3 when I run them - adding package-lock.json should ensure that we're all using the same sub-dependencies. I have no specific reason to think that users having different sub-dependencies installed is the issue in #465 - it just eliminates one possibility.