W-17156076 Using NativePRNG in place of SHA1PRNG

[sf-sunnymittal]

Issue
As mentioned in https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE0000252OC9YAM/view, we need to remove the SHA1PRNG algorithm as this is not safe to use.

Fix
Made changes to mark the SHA1PRNG as deprecated. We will remove this as part of a major release.

Changes Done

1. Updated the SHA1PRNG option to SHA1PRNG_Deprecated
2. Updated all test cases to use NativePRNG

[sabecasissf]

I thought I had already added this comment, but it seems not. Since we are going to be maintaining customers with SHA1PRNG for a while, even when it is deprecated, shouldn't we leave some tests with SHA1PRNG value?

[sf-sunnymittal]

I thought I had already added this comment, but it seems not. Since we are going to be maintaining customers with SHA1PRNG for a while, even when it is deprecated, shouldn't we leave some tests with SHA1PRNG value?

Earlier all the tests were running with SHA1PRNG even though we have 4 options for PRNG algorithm. Not sure if it is ok to just test out the things with 1 Algorithm or we should have test cases for each implementation.

[sabecasissf]

I thought I had already added this comment, but it seems not. Since we are going to be maintaining customers with SHA1PRNG for a while, even when it is deprecated, shouldn't we leave some tests with SHA1PRNG value?

Earlier all the tests were running with SHA1PRNG even though we have 4 options for PRNG algorithm. Not sure if it is ok to just test out the things with 1 Algorithm or we should have test cases for each implementation.

I was just thinking, maybe not, if we can identify a different code path in the connector for any of those algorithms, then yes, but otherwise, I think we are good and you can disregard my question.