Do not depend on Sentry for scripted runs

[fermuch]

Currently, all calls to the CLI wait for sentry events to be sent (by calling sentry.Flush).

If the command is run from an isolated environment with no network, the CLI will always hang for at least 2 seconds before closing, making it unusable in a scripted/automated setup.

It would be very helpful if there was no dependency to Sentry, or at least, a way to disable it (maybe add a --no-network to prevent network access?).