Improve logging output

[tillrohrmann]

We should revisit what the runtime logs on the various log levels to make sure that it gives enough information to the user and that the information makes sense.

Tasks

Preview Give feedback

1. State machine logging
2. Invoker/invocation task logging
3. Enable restate=info logging by default when no RUST_LOG env is set
4. Hide reflections logs for io.grpc and dev.restate type collisions
5. Remove noisy repetitions of service invocation id in effects logging Keeping them for the time being

[slinkydeveloper]

One thing related to logging that annoys me is that i cannot easily filter restate logs at verbose level compared to other logs. We need to check how we can have something like a restate prefix on all the logs we generate from our code, in order to allow define log filters such as RUST_LOG=info,restate=debug. Perhaps this might simply boil down to adding a prefix to all our modules (which is something we wanted to do anyway)?

[slinkydeveloper]

Just tried this RUST_LOG=info,hy=debug and apparently it catches all the hyper logs, and filters out the restate logs lower than info. I guess by naming all our crates with the prefix restate_ we can simply configure logging with RUST_LOG=info,restate=debug

[tillrohrmann]

Interesting @slinkydeveloper observation. Yet another reason for prefixing our crates with restate.

[slinkydeveloper]

@tillrohrmann #295

[tillrohrmann]

Close as done for M1A.