launcher_log.txt can fill the disk if sentry.io cannot be reached

If the domain "sentry.io" is blocked on a network (such as by AdGuard, PiHole, VPN, etc.), when the launcher attempts to reach sentry.io, the query fails. The launcher handles this by re-querying an unlimited number of times. This results in the error message being written to the log file launcher_log.txt which quickly grows in size and can fill an entire disk.

As an example, on my machine, the combined size of the 10 launcher_log.txt files is currently 73 Gibibytes (and growing by many Mibibytes each second as long as the launcher stays open).

I deleted these log files, re-launched the launcher, and attached the log file that was generated as a reference. In the log, the following text is repeated:

[Info: 2024-07-09 03:05:35.896617738: NetQueue.cpp(213)] NetQueue: Starting net action https://sentry.io/api/2703928/store/
[Error: 2024-07-09 03:05:35.896686177: CurlNetQueue.cpp(574)] NetQueue: No ip address available. Error code 7, Host: sentry.io
[Error: 2024-07-09 03:05:35.896700327: CurlNetQueue.cpp(649)] NetQueue: Action failed with result "Failed to connect to sentry.io port 443 after 0 ms: Couldn't connect to server" (7) : https://sentry.io/api/2703928/store/