fix: Handle Sentry connection errors gracefully during gdk install

When Sentry cannot connect to new-sentry.gitlab.net (e.g., due to network issues or timeouts), the error is fatal and prevents gdk install from completing successfully. Since Sentry is only used for telemetry/analytics, we should log a warning instead of crashing.

This wraps both Sentry initialization and the at_exit close handler with error handling to gracefully degrade when the Sentry service is unreachable.

Error fixed:

Failed to open TCP connection to new-sentry.gitlab.net:443 (execution expired)

Changes:

• Wrap Sentry.init in try-catch to handle initialization failures
• Wrap Sentry.close in the at_exit handler to handle connection timeouts
• Log warnings instead of crashing when Sentry is unreachable