Let BlenderSetupUtils.verifyBlenderBinary fail gracefully instead of getting stuck

[smlpt]

Newly downloaded Fiji with only Mastodon and Mastodon Tomancak packages installed. The "Setup Blender Addon..." button doesn't open a new window with the setup, as was previously the case.

[smlpt]

I fixed it by cloning the repo and debugging through the code. The problem was an addon that caused a crash inside the command line usage of Blender, but not when opening the Blender.exe as usual (where it failed silently).

With the failing addon, BlenderSetupUtils.verifyBlenderBinary() got stuck forever and didn't catch and proceed as expected. So maybe this method should be overhauled to improve the user experience.

The consequence was that I didn't even get access to the setup menu to change the Blender path to something else, so I was locked out. I had to disable the faulty addon to bring back the setup wizard.

[smlpt]

The same issue occurs again when trying to select a Blender executable in the setup wizard and there is an exception with an addon. The user isn't notified about anything going wrong, but the setup will be stuck until it is forcibly closed.

[maarzt]

Thank you @smlpt for reporting the bug.

Improving the code to fail more gracefully and providing a better error message would certainly be desirable.

Could you add some details, how to reproduce this bug?
Or if you like, suggest a PR?

[smlpt]

I sadly can't seem to reproduce it on my side anymore. I had an outdated version of Molecular Nodes running on Blender 5.0, which crashed. After reinstalling the addon, this was fixed. On my private machine Grid Modeler (a paid addon) failed in headless mode because of some function that wanted to render UI, but since it is paid I can't use it for reproducing either. The NotebookConnector addon also throws an exception, but the verification passes regardless since the print statement is still found in the output.
I reinstalled an old MolecularNodes version that crashes during the headless startup, but the selection of the exeuctable still works now. So I don't really know why it froze earlier, but not anymore. Which is still a good thing, I guess?

Not sure if the issue can be closed for now and reopened if anyone stumbles upon this again?