fix: nodemailer - email to an unintended domain can occur due to interpretation conflict. (#15356)

Resolves [Dependabot Alert
289](https://github.com/twentyhq/twenty/security/dependabot/289) and a
couple other alerts.

Removed types for `imapflow` since the package ships them internally
now. `yarn.lock` has major changes due to an upgraded AWS SDK
`@aws-sdk/client-sesv2` which is used by Nodemailer 7.

- No breaking changes were introduced in imapflow and mailparser. 
- Nodemailer's breaking change was dropping the legacy SES transport; we
already use the SMTP transport + our own AWS SES client, so nothing else
needs changing.

package.json

@@ -113,7 +113,6 @@
     "@types/express": "^4.17.13",
     "@types/fs-extra": "^11.0.4",
     "@types/graphql-fields": "^1.3.6",
-    "@types/imapflow": "^1.0.21",
     "@types/inquirer": "^9.0.9",
     "@types/jest": "^30.0.0",
     "@types/lodash.camelcase": "^4.3.7",
@@ -130,7 +129,6 @@
     "@types/lodash.pickby": "^4.6.9",
     "@types/lodash.snakecase": "^4.1.7",
     "@types/lodash.upperfirst": "^4.3.7",
-    "@types/mailparser": "^3.4.6",
     "@types/ms": "^0.7.31",
     "@types/node": "^24.0.0",
     "@types/passport-google-oauth20": "^2.0.11",