Improve ROCm 5 support about chapel

[stonea]

Also note that we currently error (in Chapel) when users use atomicMax/Min with 64-bit signed integers as this wasn't supported by HIP until ROCM 5.7 (ROCm/clr#2).

Once we're able to support 5.7 and on, we'll need to decide which of these we'll want to do:

• Just require the newer ROCM 5.7 going forward (it's less work on our part but in practice machines might be using out-of-date versions)
  • if so, should we have bundled versions of hip / cuda like we do for our other third party deps?
• Continue supporting earlier versions of ROCM and do a checks at compile time to error/warn when using feature incompatible with the current version.

I'm leaning towards just adding our own check and only erroring when using an incompatible version.

[e-kayrakli]

I am wrestling with some ROCm version issues, and wanted to record the following table to summarize ROCm versions and which Clang version they correspond to. The list is not exhaustive and contains ROCm installations that I have easy access to.

ROCm Version	Clang Version
4.2.0	12.0.0
4.4.2	13.0.0
5.2.3	14.0.0
5.3.3	15.0.0
5.4.3	15.0.0
5.6.1	16.0.0