feat(logger): use RUST_LOG-like EnvFilter for logging

[Erigara]

Description

Replace level filter with EnvFilter which support setting specific log level for different iroha modules.

Examples

The same can be done through configuration in config.toml.

# set global logging level to debug
LOG_LEVEL="debug" ./scripts/test_env.py setup
# set global logging level to error and info for iroha_core
LOG_LEVEL="error,iroha_core=info" ./scripts/test_env.py setup
# receive only logs from sumerag with trace level or heigher
LOG_LEVEL="iroha_core::sumeragi" ./scripts/test_env.py setup
# receive all logs at trace level, except axum for which use error
LOG_LEVEL="trace,axum=error" ./scripts/test_env.py setup

Linked issue

Closes #4829

Benefits

More granular control over logging.

Downsides

It's harder to check correctness for example if someone would write LOG_LEVEL=infa iroha won't return any error because this would be parsed as accept logs from module infa at trace level.

I believe we can mitigate this, by custom parsing, but it would make our type more strict than orginal EnvFilter.
It's smt i would prefer to leave for separate PR.

[github-actions]

@BAStos525

[Erigara]

@BAStos525 this change is backward compatible, so previous values for LOG_LEVEL and configuration will continue to work.

[mversic]

It's harder to check correctness for example if someone would write LOG_LEVEL=infa iroha won't return any error because this would be parsed as accept logs from module infa at trace level.

why is default TRACE?

[Erigara]

It's harder to check correctness for example if someone would write LOG_LEVEL=infa iroha won't return any error because this would be parsed as accept logs from module infa at trace level.

why is default TRACE?

idk, lowest possible level is assumed by tracing crate