AIO DX subcloud collect fails if any of its system node collects fail

[Eric MacDonald]

Brief Description
-----------------
Collect of subclouds are considered to be an 'orchestrated' collect initiated from its managing System Controller.

collect --subcloud <subcloud name>

The overall subcloud collect is seen to fail if any of the subcloud's system node collects fail.
This is not desirable behavior.

Instead, the subcloud collect should still succeed and produce local collect.log logs that indicate if and why any of its local system nodes collects fail.

Severity
--------
Major: subcloud collect will fail if any of its system node collects fail.

Steps to Reproduce
------------------
Run subcliuyd collect when one of its system nodes is unreachable.

Expected Behavior
------------------
subcloud collect succeeds with tarball that excludes the hosts that failed

Actual Behavior
----------------
Overall subcloud collect fails

Reproducibility
---------------
Reproducible

System Configuration
--------------------
AIO SX subcloud

Branch/Pull Time/Commit
-----------------------
Any prior to resolution of this issue report.

Last Pass
---------
Never

Timestamp/Logs
--------------
 collect all --subcloud subcloud3
[sudo] password for sysadmin:
collecting data from 3 subcloud(s)
monitoring subcloud collect ; please standby
Error: failed to collect from subcloud3 [remote] (reason:1)
collected subcloud1_20230405.181859 ... done (00:01:44 37M 26%)
collected subcloud2_20230405.181859 ... done (00:01:47 36M 27%)
collected from 3 subclouds
creating all-subclouds tarball /scratch/ALL_SUBCLOUDS_20230405.181859.tar ... done (00:01:47 73M 27%)

Test Activity
-------------
Normal Use trying to collect from an AIO DX subcloud

Workaround
----------
SSH to subcloud, run a local collect and manually scp the subcloud collect bundle off system.