Update dependency nodemailer to v6.9.11

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nodemailer (source)	`6.9.10` -> `6.9.11`

Release Notes

nodemailer/nodemailer (nodemailer)

### [`v6.9.11`](https://togithub.com/nodemailer/nodemailer/blob/HEAD/CHANGELOG.md#6911-2024-02-29) [Compare Source](https://togithub.com/nodemailer/nodemailer/compare/v6.9.10...v6.9.11) ##### Bug Fixes - **headers:** Ensure that Content-type is the bottom header ([c7cf97e](https://togithub.com/nodemailer/nodemailer/commit/c7cf97e5ecc83f8eee773359951df995c9945446)) ### [`v6.9.10`](https://togithub.com/nodemailer/nodemailer/blob/HEAD/CHANGELOG.md#6910-2024-02-22) [Compare Source](https://togithub.com/nodemailer/nodemailer/compare/v6.9.9...v6.9.10) ##### Bug Fixes - **data-uri:** Do not use regular expressions for parsing data URI schemes ([12e65e9](https://togithub.com/nodemailer/nodemailer/commit/12e65e975d80efe6bafe6de4590829b3b5ebb492)) - **data-uri:** Moved all data-uri regexes to use the non-regex parseDataUri method ([edd5dfe](https://togithub.com/nodemailer/nodemailer/commit/edd5dfe5ce9b725f8b8ae2830797f65b2a2b0a33))

Configuration

📅 Schedule: Branch creation - "after 8am and before 5pm on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: delta@1.14.6
npm ERR! Found: @angular/animations@17.2.1
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.2.2" from the root project
npm ERR!   peerOptional @angular/animations@"17.2.1" from @angular/platform-browser@17.2.1
npm ERR!   node_modules/@angular/platform-browser
npm ERR!     @angular/platform-browser@"17.2.2" from the root project
npm ERR!     peer @angular/platform-browser@"17.2.1" from @angular/forms@17.2.1
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"17.2.2" from the root project
npm ERR!     2 more (@angular/platform-browser-dynamic, @angular/router)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @angular/animations@"17.2.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/core@17.2.2
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"17.2.2" from @angular/animations@17.2.2
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"17.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-03-05T14_42_11_779Z-debug-0.log

mycomplexsoul / delta