Remove all thrown exceptions in Dartagnan.main()

[hernanponcedeleon]

This solves some SVCOMP problems in which the runner was looping forever e.g., if we would pass the wrong file path.

However, we still have the looping problem if dartagnan runs OOM. It seems the jvm returns 1 as exit code, which is the same value we use for ExitCode.BOUNDED_RESULT (which is also what we used for the looping condition in the runner).

[ThomasHaas]

I think we should simply use different exit codes and avoid the common one's like 1 (see here for some examples). I also asked ChatGPT and it mentions that several of the lower numbers 0-4 are used. I would play it safe and use exit codes starting at 30 or so.

[ThomasHaas]

I think we should just put UNKNOWN_ERROR on exit code 1, and then even if we have uncaught exceptions or the JVM runs out of memory, the error code is fine.
But I guess that any changes in the exit codes would require you to update Vsyncer again?

[hernanponcedeleon]

I think we should just put UNKNOWN_ERROR on exit code 1, and then even if we have uncaught exceptions or the JVM runs out of memory, the error code is fine.

As you said, that will break vsyncer. However, it might indeed be the best solution. Since there is no hurry for these changes, I will put the PR on hold until we also rework all options (which will also have some breaking changes); then we can make a new release with major version update

[ThomasHaas]

The changes in this PR conflict with #1022. I think #1022 will get merged before this one and then you will need to "reapply" the changes, so maybe we should just close this PR for now.