Add legate-issue command for collecting issue info

[bryevdv]

This PR adds a new entry point legate-issue that prints out information that is useful for GitHub issues. We can create a GH issue template to suggest (or require) including the output of this command up-front.

Sample output on my system:

dev310 ❯ legate-issue 
Python      :  3.10.11 | packaged by conda-forge | (main, May 10 2023, 18:58:44) [GCC 11.3.0]
Platform    :  Linux-5.14.0-1042-oem-x86_64-with-glibc2.31
Legion      :  v23.11.00.dev-16-g2499f878
Legate      :  23.11.00.dev+17.gb7b50313
Cunumeric   :  (ImportError: cannot import name 'LogicalArray' from 'legate.core')
Numpy       :  1.24.4
Scipy       :  1.10.1
Numba       :  (not installed)
CTK package : cuda-version-11.8-h70ddcb2_2 (conda-forge)
GPU Driver  : 515.65.01
GPU Devices :
  GPU 0: Quadro RTX 8000
  GPU 1: Quadro RTX 8000

As it stands the code is fairly bare-bones. @manopapad if you'd like it to be more bulletproof I can continue to robustify it. We can also add more output now or in the future as new bits of important context arise.

[bryevdv]

@manopapad please check again on OSX, I've modularized things a bit as well.

[bryevdv]

@manopapad do you happen to know if this message

[0 - 7ff84ee47700]    0.000177 {4}{threads}: reservation ('CPU proc 1d00000000000003') cannot be satisfied

is on stderr? If so we could probably just redirect stderr to a hole

[bryevdv]

@manopapad one last quick change to hopefully get rid of that not-relevant-here warning

[manopapad]

@manopapad one last quick change to hopefully get rid of that not-relevant-here warning

Didn't help. This is coming from Realm on MacOS, because that OS doesn't allow us to pin cores. We could suppress warnings from that module ("threads") in the Legate launcher, but I think this will become a non-issue soon, once we have dynamic resource discovery in Realm.

[bryevdv]

:+1: reverted, will merge when green