That is a 32 hex characters. 32 x 4 is 128 bits. The hashes that Oracle publishes (e.g. here https://www.oracle.com/webfolder/s/digest/8u301checksum.html) are SHA256 and MD5 ... and none of them match that what is in that URL.
My guess is that Oracle are deliberately using UIDs in the URLs to make it hard for users to download a JRE or JDK without using an Oracle account and signifying that they have read and agree to the license terms. It would be self-defeating for them to make it easy for users to work out what the UIDs are going to be. With SHA512, they can make it effectively impossible, and I don't see why they wouldn't do that.
If this is problematic for you, my advice would be to download the installers that you need by hand and save a copy in your own private infrastructure. Then set up your Chef cookbook to deploy Java from your private copy. Note that this is the recommendation here:
and this cookbook specifically supports this way of handling the problem.
Alternatively, use an alternative to Oracle Java that doesn't make scripted Java installation difficult.