feat: timeout and log latest action during init

[MCozhusheck]

Description

Timeout if initialization took too long and report to sentry the last action. Timeout is for each binary and is set to fixed value of 5 minutes.
Another big change is that app will exit and show error if timeout was exceeded. Previously user would be stuck at initialization screen.

Closes: #1170

Motivation and Context

Some users reports being stuck at initialization screen. The underlying reason is unknown and we need to increase the logging and sentry reporting.

How Has This Been Tested?

Decrease timeout to like 20 seconds and add this line in binaries_resolver.rs in initialize_binary function to fake timeout on one selected binary:

match binary {
    Binaries::Xmrig => {
        println!("Sleeping for 30 seconds");
        sleep(Duration::from_secs(30)).await;
        println!("Waking up");
    }
    _ => {}
}

What process can a PR reviewer use to test or verify this change?

Same as above

Breaking Changes

• None
• Requires data directory on base node to be deleted
• Requires hard fork
• Other - Please specify