Prevent UrlRewriterParseException from being wrapped in RuntimeException

[AlexTereshenkov]

When attempting to run a Bazel command, Bazel server will shutdown and exit with an unexpected error when the downloader config is invalid:

$ echo "#test\nfoo" > bazel_downloader.cfg
$ cat bazel_downloader.cfg                                                                                                 
#test
foo
$ bazel-dev build //... --downloader_config=bazel_downloader.cfg
< exits immediately with the Bazel server killed >
$ echo $?
37

37 corresponds to Unhandled Exception / Internal Bazel Error as per the docs.

This PR introduces changes that will let catch and rethrow UrlRewriterParseException before Closer.rethrow() to prevent it from being wrapped in RuntimeException.

$ bazel-dev-fixed query //... --downloader_config=bazel_downloader.cfg 
...
ERROR: Failed to parse downloader config at bazel_downloader.cfg:2: Unable to parse: foo
$ echo $?                                 
2

[gemini-code-assist]

Code Review

This pull request aims to prevent UrlRewriterParseException from being wrapped in a RuntimeException by adding a specific catch block. While the intent is correct, the current implementation introduces a bug related to exception suppression with com.google.common.io.Closer. My review includes a critical comment with a suggested fix to correctly handle the exception without breaking suppression, ensuring that no exception information is lost.