chore(deps): update dependency nlog to 5.3.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
NLog (source)	5.3.3 -> 5.3.4

---

Release Notes

NLog/NLog (NLog)

v5.3.4

Improvements

• #​5572 Layout.FromMethod that supports typed Layout (#​5572) (@​smnsht)
• #​5580 Layout.FromMethod that supports typed Layout (without boxing) (#​5580) (@​snakefoot)
• #​5570 ScopeContextPropertyEnumerator - Optimize HasUniqueCollectionKeys (#​5570) (@​snakefoot)
• #​5571 XmlLayout - Fixed bug in handling unsafe xml property names (#​5571) (@​snakefoot)
• #​5573 FuncThreadAgnosticLayoutRenderer - Implement IRawValue (#​5573) (@​snakefoot)
• #​5577 Introduced OnConfigurationAssigned to signal activation of LoggingConfiguration (#​5577) (@​snakefoot)
• #​5578 Update copyright to 2024, and removed trailing white spaces in source code (#​5578) (@​snakefoot)
• #​5585 Fixed various issues reported by EnableNETAnalyzers (#​5585) (@​snakefoot)
• #​5587 NetworkTarget - Added SendTimeoutSeconds to assign TCP Socket SendTimeout (#​5587) (@​snakefoot)
• #​5588 DateLayoutRenderer - Optimize for Round Trip ISO 8601 Date Format = o (#​5588) (@​snakefoot)
• #​5589 LayoutRenderer - Changed Render-method to use StringBuilderPool (#​5589) (@​snakefoot)
• #​5599 JsonLayout - Refactor code to simplify rendering of scope properties (#​5599) (@​snakefoot)
• #​5600 JsonLayout - Precalculate Json-Document delimiters upfront (#​5600) (@​snakefoot)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.