Description

make sysinfo more robust

change

• fix when using commang line arg --dump-sysinfo some info are missing
• • Implement fallback methods and or error handling when retrieving a certain information
• • ModuleNotFoundError: No module named 'psutil' and so --dump-sysinfo failed
• restructure import with error handling
• • move complex modules such as shared and extensions into function level input
• • use shared_cmd_options over shared.cmd_opts for cmd_opts
• add new info git -C <webui_rooot> status
• • this provide information on the better or not there is non-committed changes to the code base
• • using pip freeze --all with importlib.metadata as fallback for listing pacages
• • pip freeze provides extra information such as if the package was installed via a custom wheel URL as opposed to only the version, example:
    "triton @ https://github.com/aaa/bbb/releases/download/v1/xxx.whl#sha256=abcde",
• • importlib.metadata because pkg_resources is being deprecated
• .gitignore /sysinfo-????-??-??-??-??.json
• • file is created when using --dump-sysinfo

idea
including ui-config.json might be valuable as well

discussion

I think the term sysinfo is confusing in boath the UI and in the issue post template
I belive this increases the chance of those who don't read carefully to just onput something like

Windows
Nvidia
Chrome

as opposed to a generating and uploading the sysinfo we want
I think something like diagnosis info debug info might work better

most likely they're a better terms then the ones I came up with

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests