chore(deps): bump electron-log from 4.4.8 to 5.1.7

[dependabot[bot]]

Bumps electron-log from 4.4.8 to 5.1.7.

Changelog

Sourced from electron-log's changelog.

Changelog

5.1.0

• New entry point for NW.js / Node.js apps: 'electron-log/node'

5.0.0

Core

• Now it's a time to use modern ES instead of ES5. It was a joy to use old-fashioned ES5, but since the library grows it becomes harder to follow its restrictions. Starting from v5 the library requires Node.js 14+ or Electron 13 at least.
• Now a renderer process just sends log data to the main through IPC, so only the main logger can be configured. See initialize for more information
• A new tranforms property is added for each transport. It allows to configure transformations preformed on message data. See transforms for more information.
• log.create(logId) is replaced by log.create({ logId })

File transport

• archiveLog options is renamed to archiveLogFn
• resolvePath options is renamed to resolvePathFn
• All logs are written to main.log file. If you want to write renderer logs to a separated file, you can do that by overriding resolvePathFn

Console transport

• writeFn callback is added. By default, it just passes message.data to console.log function

Remote transport

• onError is renamed to processErrorFn({ error, message, request })
• transformBody is renamed to makeBodyFn({ logger, message, transport })

Electron event logger

To simplify app debugging the Electron event logging was implemented.

4.4.0

• Disable auto-loading of electron-log in the main process for using by ipc transport

4.3.0

• Add transport.file.inspectOptions

... (truncated)

Commits

• 5ecef34 5.1.7
• 80f8f63 fix(file): Unable to restrict the log file permissions, fixes #430
• 38ad749 5.1.6
• 90bfeec chore(e2e): Hide app windows on e2e test
• f762eb4 fix(file): Variables not interpolated, fixes #429
• d4e1381 feat(docs): Describe initializing in preload script, #428
• 767e92b feat(docs): Describe scope padding, closes #424
• ecb92d8 5.1.5
• 500ccab fix: Add workaround when appName can't be read, fixes #418
• 957406d chore: Exclude specs from publishing
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #8611.