Probe logging service endpoint readiness before Podman commands execution

[PavelSosin-320]

Podman uses systemd-journald service as logging backend on the systemd-based platforms like Fedora desktop. Even systemd-journald is very reliable it is started asynchronously. It doesn't happens too fast. In the case of error CRun and Conmon may try to record something into the log but fail and very important for the maintenance and bug correction data may be lost and become not recoverable. The risk of recursive error also exists. It will be more convenient to check logging service in the preemptive way, using stat journald socket for example on the top of CLI logic or during podman info command execution in the context of User's session and generate panic message saying that "logging service is down and Error data may be lost - check journald service status".