Improve Debugging UX: Push ocihook Logs to Syslog

### Description

Currently, the logs generated by `nerdctl internal oci-hook ` are not displayed in the containerd logs. This appears to be because the ocihook command runs in a separate shell, causing the logs to be lost.

This makes debugging issues in the ocihook implementation challenging, as there is no straightforward way to access these logs.

### Steps to reproduce the issue

1- trigger `nerdctl internal oci-hook ` by `run` or `create` a container
2- logs are not printed to console

### Describe the results you received and expected

Logs from `ocihook` should be pushed to syslog for better accessibility and debugging.

Benefits:

- Enhanced visibility into ocihook operations.
- Easier debugging of issues related to ocihook.
- Improved developer experience when working with nerdctl.

### What version of nerdctl are you using?

main

### Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

### Host information

_No response_