feat: wrap app with logger to duplicate stderr to syslog

[grouville]

This PR experiments the wrapping of the registry-redirect app with the logger (https://man7.org/linux/man-pages/man1/logger.1.html) utility. We just wrap the binary at the publish step, with a debian buster-slim instance (alpine doesn't have all the proper dependencies to make rsyslogd work, or at least, I tried and figured out it would take some time to debug).

As a debug step, I am currently redirecting all the outputs to my ngrok address, linking to a local vector instance. Everything works as expected, even though I am getting errors after some time (we will need to dig into that):

In test prod: https://fly.io/apps/dagger-registry-2023-07-28. To test it out: visit dagger-registry-2023-07-28.fly.dev

[grouville]

Actually, it seems that we cannot recover the logs when rsyslog drops the connection. We might need to extend it's configuration to check that + use the process as suggested earlier today by gerhard (acts as a supervisor)

Open questions:

1. Is it at the rsyslog configuration level (probably)
2. Is it at the fly process level (potentially too)

[grouville]

Following a verification with Gerhard, this has been deprecated in favor of #5. Even though this solution is elegant, we had some intermittent disconnect with the remote syslog server. Adding a new layer meant another layer to monitor and no control over the behavior on the server connection.

Moving the logic at the app level is now preferred