Fix components startup

[kozlovsky]

This PR fixes the following problem: it becomes impossible to close Tribler when a component's run method raises an error.

The reason for this behavior is the following:

1. Session was started with the default failfast=True option;
2. Its start method propagates the first exception from a failed component.run method;
3. Tribler core event loop exits before Tribler GUI establish a connection with Core;
4. Tribler GUI tries to connect with Core and waits indefinitely, ignoring attempts to close it.

The desired behavior is the following:

1. If some component crashes on start, Tribler should run anyway because the remaining functionality with a failed component may still satisfy the user's needs.
2. The error raised during the component's start should be passed to the GUI to be reported in the usual way to Sentry if the user agrees.
3. One component's fail can cause cascade failures of other components. These failures should not be reported as they are secondary.

This PR does the following to fix the problem:

1. It starts Session with the failfast=False option.
2. When an exception is raised by a component's run method, it is raised again in a separate branch to be processed by Sentry (raising it in the original branch will stop the event loop).
3. New should_stop field was added to the exception's notification from Core to GUI to prevent automatic stopping of Tribler after the error was reported to Sentry.

As an example of error, the case of TagsDatabase failure was considered caused by the incorrect structure of tables. I added defensive checks to other parts of the code in a separate commit so Tribler could successfully start even if TagsComponent could not run.

As a separate commit, I added a possibility to have errors reported from Core to GUI, which are not critical enough to cause Tribler shutdown, so they are passed with the should_stop=False flag. In case of repeating errors, new occurrences will be suppressed silently not to disturb the user interface.

Also, I noticed that errors in REST API are not reported to Sentry and displayed to the user in a separate dialog window. It is too big a task to be included in this PR, so I added a TODO option and will open a related issue.

Related to #6263

[drew2a]

Great work!

I wrote some comments about the PR and Pylint and Flake8 should be satisfied before PR can be merged.

[kozlovsky]

I changed the logic for the component to have tribler_should_stop_on_component_error flag which is True by default. If it is set to False, Tribler will continue working even if the component crashed with an error.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.1% Duplication