🐛 Bug Report: "credentials.senderName" is ignored in some providers

[ArturHamannRonconi]

📜 Description

As with the following issues there is an issue when trying to add a credentials.senderName to some providers.

• 🐛 Bug Report: Sendinblue provider ignores credential.senderName #1813
• 🐛 Bug Report: Sendgrid provider ignores credentials.senderName #1417

One of the providers with this error that I noticed was AWS SES, I am also creating a pull request resolving this specific bug

Note: as soon as I finish the pull request, I will add its link here, based on the following pull request, I believe that you can do the same for other providers

• fix: take into account credentials.senderName in sendgrid provider #1418

👟 Reproduction steps

1 - Clone the application
2 - Execute the following commands to setup local

• npm run setup:project
• npm run start:api:dev
• npm run start:web
  3 - Create an account
  4 - On the Integrations tab select AWS SES
  5 - Add the necessary information and the senderName you want
  6 - Create a template and with a trigger for an email
  7 - In the last step of editing the email template, test it by sending the email to yourself

👍 Expected behavior

The expected behavior is that the email is sent with the name chosen when creating the integration
Example:

👎 Actual Behavior with Screenshots

What currently happens when the email is received it adds a name by default of 'no-reply'
Example:

💻 Operating system

Linux

🤖 Node Version

16.15.0

📃 Provide any additional context for the Bug.

Edit: 1 Here is the Pull request created

• fix: use sender name with from email in ses provider #2226

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

Yes I am willing to submit a PR!