Prevent file logging before configuration initialization

[rubo]

Changes

This PR prevents file logging before configuration initialization. The reason is that now Nethermind uses the log rules at the very beginning to avoid having sudden log style changes after loading the configuration. However, on some user configurations, the Nethermind directory is inaccessible for the Nethermind process, and that causes an error.

Another approach might be writing that part of the logs in the user's temp directory. But till now, that logs were missing, and perhaps having them in the file somewhere is not that useful.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Tested manually.

[MarekM25]

Do you know which PR could add this bug? It would be easier to understand the fix

[rubo]

Do you know which PR could add this bug? It would be easier to understand the fix

I don't recall which one exactly, but one of mine. Logs have been changed from this

to this

so they have their colors and formatting right from the start.

Since the configuration is not initialized at that early stage, the logger instance logs in the default data directory, i.e., the Nethermind directory. And for some setups, it causes access issues. Thus, this PR disables file logging for that stage (like we had previously) while keeping the nice logs.