RFE: pre-registration connectivity check, or post-registration-attempt error reporting to server

A client is attempting to register landscape-client machines at a remote location to their On-Prem Landscape server in a semi-automated way. Sometimes the registration requests are unsuccessful. At this time, access to check the broker.log on the client is not possible due to the remote nature of the client machines.

The request here is to have the landscape-config command either produce a pre-registration connectivity check that is logged on the server side, or to otherwise attempt to report any registration errors to the server. The goal is to see from the server if a client machine tried to register and had some issue preventing the registration request from succeeding.

A simple PoC might be a curl request something like this, logged in the Apache logs, or otherwise noted by the server side:

curl -sk https://ubuntu-mini/${HOSTNAME}_INFO_connectivity-check
curl -sk https://ubuntu-mini/${HOSTNAME}_ERROR_${ERROR_MSG}

Obviously if both the connectivity check, and the error message are not logged, then this would confirm that a connectivity/firewall/access issue is occurring, and further action would be needed by the user. However, this would give insight into potential issues where an automated remote registration request fails for some reason.