Drop separate logger initialization

[sagikazarmark]

Overview

This PR simplifies how logging is initialized in the application to increase conformity with standards (OpenTelemetry in this case).

There is a cost however: if the application initialization fails, there is no logger to notify us about that failure (and it will never reach any OTLP exporter, since the "real" logger doesn't get initialized until the whole application initialization is done).

As a compromise, we initialize a basic JSON logger, since JSON is used in most production environments. If anything goes wrong during app init, that logger prints the error to stderr.

The recommended approach to deal with app init failures is to have additional monitoring in place that watches over running instances of an application. If there is a crash loop, you know something is up and can directly examine pod logs.

If you have a file based log collector in place (eg. fluentbit/fluentd), you can collect the JSON logs and forward them to your log analytics system.

We may revisit this decision in the future, but for now, we feel this is an acceptable compromise.

Notes for reviewer