Connect errors without specific handling triggered while doing a check for updates to our error report dialog

[dalthviz]

Most probably a generic exception is due to an internal Spyder error. So, we need to connect this to our error report dialog. But since the code related to updates diverged significantly between 5.x and master, I think it's better to leave this for master.

Should an issue be open for that or maybe and issue tracking that already exists @ccordoba12 ?

Originally posted by @dalthviz in #21868 (comment)

Connect catched Exceptions that are not shown in a dialog when checking for updates to the Spyder error report dialog

[ccordoba12]

@mrclary, could you take care of this one?

[mrclary]

I included the fix in #21836