Add ValidateReleaseCdnChecksumAggregateJob to the post release validation

This step currently check the published release.json with sha.txt file and try to validate if there are the same sha512 hash values. That make sense. But it was placed in the middle of release process when the releases.json file was not properly released yet.

## Goal

We need to add this to the post-release-validation pipeline and check all the hash values consistency there.

## Steps

- Validate the sha512 bare files published to CDN aside to the binary file with the value which is manifests (release.json, releases.json)
- Validate these values also against text sha.txt files for each version.