Add secure_random functions

[darrenfu]

Currently all presto random() functions return a pseudo-random number.

Implement secure_random() functions returning a cryptographically secure random number between lower (inclusive) and upper (exclusive).

Test plan - unit tests and verifier run

Fill in the release notes towards the bottom of the PR description.
See Release Notes Guidelines for details.

== RELEASE NOTES ==

General Changes
* Add secure_random() and secure_random(lower, upper) with uniform distribution.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Darren Fu (b43ea70a2879f0e225d39d28cfdf7a2546a2a359, bcb267349ca60d5cf5b39a296735a55988a4046c, 01aacb333440e8ae2a84fa4a28c307df9b36aede, 7aa41abd39c475b4b4e7a0f6277a2a66d137e6c4)

[rschlussel]

I'm not sure we want to catch a noSuchAlgorithmException because it means we would basically never know if NativePRNGNonBlocking wasn't being used. It would be better to throw an internal error.

[darrenfu]

Thanks for reviewing my PR!
Actually NativePRNGNonBlocking is an OS specific secure random implementation. See this post.
I will extract the os-specific secure random algorithm as a static variable then.

For exception handling, I can definitely wrap NoSuchAlgorithmException into a PrestoException and throw it.

[rschlussel]

Also, we avoid merge commits. Can you rebase your change on master instead?