Trail of bits audit - Issue #3 (Improper error handling)

[isSerge]

Introduced new error titles:

"Failed to initialize autolauncher",
"Failed to initialize updater",
"Failed enabling autolauncher",
"Failed disabling autolauncher",
"Failed to get logs",
"Failed to initialize config",
"Failed to reset the application",
"Failed to start plotting"

Draft, since we need to update the current generic error message:

Please, make sure you have an Internet connection and enough disk space in order to proceed. If the problem persists, you can reach out to our team

Closes #337

[ozgunozerk]

I noticed this PR will get rid of errorLogger in many places, but we also want errors to be logged.
When I looked at setError() code in store.ts, I couldn't see any call to errorLogger()?

[ozgunozerk]

@isSerge I'm happy with it as is. However, what about embedding errorLogger(error) into the setError(error) function, so that we will only call setError() from the outside?
The code may be cleaner this way.

[isSerge]

@ozgunozerk setError does not have access to the logger, unfortunately, it seems Pinia does not support dependency injection, so we'll have to provide it as a parameter as in other methods

[isSerge]

@ozgunozerk also setError accepts objects with a title and optional message (which are displayed to users), while the logger logs the actual error, so I would prefer to keep them separate

[ozgunozerk]

did inspect during draft, looks great to me