Move self diagnostic mostly to the SDK side and add more compatibilit…

[LeiGlobus]

This refactors the endpoint specific self-diagnostic command into an executable script that is installed with the SDK.

• The old command now redirects to the new one, with a deprecation warning.
• The default is to print to console, with the -z option creating a zipfile as before.
• Some env/test related code has been moved to make it more accessible, for example _home() and ensure_compute_dir() previously in tokenstore.py (this is now in compute_dir.py, incorporated with Reid's LoginManager related PR)
• The tests in -endpoint have been moved and modified/added to in their new -sdk location
• The hardware_report.py tests are now included by default, though there were some overlaps
• Now an endpoint UUID can be specified, and the -e flag will try using the executor to run a hello world function/task on it
• The endpoint config/logs and local endpoint related info depends on whether globus-compute-endpoint is installed
• The cat() method has been slightly refactored to work outside of click.echo, and now takes a list of wildcards in order to able to sort all matched files alphabetically to group endpoint files consecutively
• Because it's installed with the SDK, potentially on non-linux systems, windows/mac equivalent have been added when there's an easy replacement, but not all commands are available in all OSes
• A few new modules (colorama etc) were used to print OS-flexible colored/highlighted text, though they are not preserved in the resulting diagnostic.txt output.

The new self-diagnostic syntax examples:

globus-self-diagnostic -k 1 -p       # the -k limits log file sizes in case giant, the -p prints output to console instead of creating a zip file
globus-self-diagnostic               # This generates a zip file and prints only the test headers that are run while they are running
globus-self-diagnostic -p -e ep_uuid # This prints to console and sends a new task to the specified endpoint UUID

[khk-globus]

Looks like a rebase is in progress. I'll continue when that's all done. Meanwhile, "comments in progress" as well! 😉

[khk-globus]

Looking good; a few minor comments. Reid has already brought up the items of any importance that stood out to me, so you two go ahead.

Beyond those, I do wonder if the default output should be minimal, along the lines of what was globus-compute-endpoint self-diagnostic -z. Right now, there's a bunch of header information for each test, which I'm thinking is largely superfluous for most users. Just the file is all that's necessary, and makes it similarly easier to reference, show, and request of users in #help. Perhaps adding -v/--verbose to emit these headers instead?

Meanwhile, I observe that at least one test appears to fail when it it's not obvious to me that it should:

$ ll /etc/os-release
lrwxrwxrwx 1 root root 21 Sep 10 07:18 /etc/os-release -> ../usr/lib/os-release

$ globus-compute-diagnostic
...
== Diagnostic: python:cat(/etc/os-release) ==
No file named -
...

But generally, I'm looking forward to getting this out -- it's a nice addition!

[khk-globus]

Hmm; this begins to imply to me that these are no longer unit tests then. Crossing the process barrier is one indication of that. Semantic, perhaps, but I wonder if we can mock an appropriate something else, fixture-ize it, or do we move these tests?

On the other hand, I'm not looking too hard at this particular test file at the moment, so I may be missing something more fundamentally obvious.

[khk-globus]

I think this is nearing the stage of bike-shedding; I'm ready to have this go in. @rjmello ?

[LeiGlobus]

Note that sometimes one of the executor tests (such as tests/unit/test_executor.py::test_executor_shutdown_cancel_futures ) fails only on PY 3.8. That test seems unlinked to any of the changes of this PR, and is an occasional failure. Furthermore, I installed 3.8.18 on both my mac and Ubuntu and that test passes repeatedly (at least 5/5 tries), so I'll attribute it to an environment weirdness and not a real failure, and re-running it til it passes is a valid strategy.