A way for us to programatically grab the MD5, SHA1, SHA256 or SHA512 of Omnibus packages
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal I think it would make sense for GitLab to incorporate some way for the end user to programatically grab either the MD5, SHA1, SHA256 or SHA512 to compare it, we are in a highly regulated infrastructure and sometime we have problems using repositories for a varied amount of reasons. We grab your packages manually though it would be nice if we could verify the package before we download it. We can do that using Ansible but we need to manually copy in the SHA512 every single time which can get a big annoying. It would be nice if we could pull it programatically either through an API call or from downloading a text file that only contains the SHA or MD5 information. <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->
issue