ROCm 5.1.1 Release!

[acxz]

I believe we have finally reached one of our biggest milestones. As of this commit, all packages in this repo can now finally be built successfully (in clean chroot to boot)! Everyone that has contributed (code or issues) should be patting themselves on the back!

Besides keeping up to date with the new ROCm releases, there are still some sizable outstanding issues (in no particular order). You can think of this as sort of a vision for how I would like to see this project and the rocm-arch community evolve.

1. push for local archlinux patches to be merged into upstream rocm packages
   I'd like for archlinux to have a reputation of being a good denizen of the ROCm community by testing code on latest deps and providing PRs and bug reports

2. provide binary packages
   Previously @petronny at https://github.com/arch4edu/arch4edu has hosted packages for us however, lately their infrastructure has been set back. I believe it might be up and running again. Having members of the rocm-arch community contribute to arch4edu to get these binary packages up again would be great. In addition, we can also try to request our packages be hosted on the more popular chaotic-aur repo. Having our packages on both can be confusing for users however and arch4edu is a better fit categorically for these packages.

3. inclusion of packages in the official Arch Linux repos
   See discussion here
   To be honest I am a bit hesitant of this. This is because 1) I like the ability of having all the packages in one place, particular for bug reports and PRs; 2) I would like Point 4 tackled first

4. try to get these packages to be reproducible
   This will require many PRs to upstream and can take a long time to accomplish. But in the meanwhile, I would like for our packages to at least have the same files packaged as the AMD deb packages.

5. get higher level libraries working on top of this
   python-tensorflow-rocm and python-pytorch-rocm would be amazing highlights (and tests) of this repo if these two ML libraries can be built successfully in chroot. hipmagma and hipsycl are other projects that I would love to see working.

6. Get other rocm projects packages
   There are still many packages of the rocm ecosystem that are missing. See: Package Request Thread #86 for more info

7. Get cuda backend hip packages packaged
   See: specify hip-runtime-amd instead of hip for deps #753 for more info about this