SSH config manipulation is a heavy operation that involves disk writing and
can take long time. Logs are added so that we can easily identify when the ssh
configuration writing is done.

During plugin initialization we have a couple of steps that are only reported in the screen.
If there is any error happening in between the steps, it is hard to identify between which steps
things went wrong without a screenshots provided by the user.

Calling onBack() in the exception handler doesn't make sense because:

- the coroutine is already interrupted by the exception
- onBack() is meant to handle user-initiated back navigation, not error recovery
- we still want the proper navigation logic but without the coroutine cancellation part