chore(deps): bump electron-log from 5.4.1 to 5.4.3 in /console/atest-desktop

[dependabot]

Bumps electron-log from 5.4.1 to 5.4.3.

Changelog

Sourced from electron-log's changelog.

Changelog

5.4.2

• #472 Add the gray color and log.transports.console.colorMap option.

5.4.0

• #465 Allow using %c template for the transports.console.format. This change may break formatting if you already use %c in your format string. In this case, you can run log.transports.console.transforms.shift() before initializing the logger.

5.2.4

• Add Buffering feature.

5.2.0

• fix: #436 log.log isn't bound to log.info. Previously, it was processed with non-existent log level.

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

... (truncated)

Commits

• 2ea69c9 5.4.3
• 9c9e16f chore(init): Warn on double initialization fixes #475
• 09504c8 chore(docs): Mark file and remote transports as main proc only, closes #473
• 4fa304d 5.4.2
• 78e92ec chore(docs): Cosmetics
• 4b90bed feat(console): Add gray ANSI color and use it for silly levels (#472)
• dc731b4 chore(e2e): Update nw installer
• 1fdcf43 5.4.1
• e051ea6 feat: Warn when electron-log/renderer is used in the main proc
• 10234f3 chore(docs): New datadog transport (#468)
• See full diff 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 <dependency name> 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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

There are 1 test cases, failed count 0:

Name	Average	Max	Min	Count	Error
	11.615372ms	12.369268ms	10.934442ms	3	0

Reported by api-testing.