blooprifle: report exit code in exception

[Flowdalic]

To help debugging, the failure code is now part of the exception in case the bloop server failed to start.

I've worked on this during debugging #1843. Turns out, knowing the exit code was not really helpful in this case. However, I believe that it is never wrong to load the exception with it.

[lwronski]

@Flowdalic Thanks for your contribution! LGTM

The error in CI is unrelated to your changes, and the Scala-CLI team will fix it soon.

[Gedochao]

@Flowdalic, the CI should pass if you rebase your branch with the newest changes from main.
The same applies to #1845

[Gedochao]

@Flowdalic it seems the following tests are failing and will need to be adjusted.

integration.test.test 3 tests failed: 
  scala.cli.integration.BloopTests.invalid bloop options passed via cli cause bloop start failure 
  scala.cli.integration.BloopTests.invalid bloop options passed via global bloop config json file cause bloop start failure 
  scala.cli.integration.UpdateTests.updating dummy scala-cli using update command 
Error: Process completed with exit code 1.

I suspect scala.cli.integration.UpdateTests.updating dummy scala-cli using update command is an intermittent connection failure, but the other 2 will need code adjustments.

BTW. let me know if you'll have trouble to find the time to fix this, in which case either me or someone else from the maintenance team will have a look.