Replaced sys.exit() with ClickException in test_connection decorator.…

[pui1ya]

Summary

This PR replaces one occurrence of sys.exit() with click.ClickException
in the network connectivity check.

Motivation

As discussed in #3676, sys.exit() bypasses Python's exception handling
and makes testing and error propagation harder. This change establishes a
pattern for handling CLI failures using Click's exception system.

Changes

• Replaced sys.exit() with click.ClickException
• No behavioral change intended (CLI still exits with an error message)

Testing

• Ran tests locally using python -m pytest
• All existing tests pass

Note: This is intended as the first incremental change before updating the
remaining occurrences.

[MoralCode]

This looks like a small, focused first PR, nice!

Could you test to make sure this works by maybe running the augur CLI uv run augur --help both with and without network connectivity to try and cause this exception to happen? I'd love to see a screenshot or something of what the new output looks like

[pui1ya]

This looks like a small, focused first PR, nice!

Could you test to make sure this works by maybe running the augur CLI 'uv run augur --help' both with and without network connectivity to try and cause this exception to happen? I'd love to see a screenshot or something of what the new output looks like

I tested the decorator by invoking a minimal Click command using 'test_connection'.

With network connectivity, command executes normally.
Without connectivity, ClickException is raised and formatted as an error.

The traceback shown is from existing logging in the decorator (print(traceback.format_exc())), and the final CLI output is handled by Click.

Screenshot attached for when there was no internet connection.

Note: I wasn't able to directly run 'uv run augur --help' locally because the CLI requires database configuration before reaching the decorator, so I tested the decorator in isolation to verify the output behavior.