Excessive error logging on first install

[cqexbesd]

Describe the bug

The first time I ran Zulip I got a lot of error logs about things that aren't really errors.

To Reproduce

1. Install Zulip for the first time (or probably rm -R ~/.config/Zulip)
2. Run Zulip

Expected behavior

Not to see these presumably invalid error messages, either seeing nothing or just a few non-error messages about new preference files being written.

Screenshots

$ zulip
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: ENOENT: no such file or directory, open '/home/andrew/.config/Zulip/Logs/enterprise-util.log'
(node:1270063) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/andrew/.config/Zulip/Logs/enterprise-util.log'
(Use `zulip --trace-warnings ...` to show where the warning was created)
(node:1270063) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: ENOENT: no such file or directory, open '/home/andrew/.config/Zulip/Logs/domain-util.log'
(node:1270063) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/andrew/.config/Zulip/Logs/domain-util.log'
(node:1270063) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
Reverting GDK_BACKEND to work around https://github.com/electron/electron/issues/28436

Desktop (please complete the following information):

• Operating System:

Arch Linux, as of this month.

• Zulip Desktop Version:

5.9.5

Additional context

Obviously this isn't the most serious of issues but debugging anything is always easier without extraneous and excessive error messages and it would give a better impression of Zulip to people who might be trying it out for the first time.