provider-email-amazon-ses doesn't support ECS task role
<!--
Hello 👋 Thank you for submitting an issue.

Before you start, please make sure your issue is understandable and reproducible.
To make your issue readable make sure you use valid Markdown syntax.

https://guides.github.com/features/mastering-markdown/

Please ensure you have also read and understand the contributing guide.

https://github.com/strapi/strapi/blob/main/CONTRIBUTING.md#reporting-an-issue
-->

## Bug report

### Required System information

<!-- Please ensure you are using the Node LTS version (18, 20, or 22) -->
<!-- Strapi v3 is no longer supported, please update to Strapi v4 -->
<!-- If you are reporting a frontend bug please provide error logs after setting STRAPI_ENFORCE_SOURCEMAPS=true in your .env -->
<!-- This environment variable makes frontend errors easier to read and trace -->

- Node.js version: Node 18
- NPM version:
- Strapi version: 4.17.0
- Database: MySQL 8
- Operating system: Docker
- Is your project Javascript or Typescript: Typescript

<!-- Did you know you can run `yarn strapi report` or `npm run strapi report` to get this information easier? -->

### Describe the bug

When attempting to use the Task Role permissions of an ECS container to send emails in strapi, I get the error:

```
{"message":"[2025-01-09 00:24:38.460] \u001b[31merror\u001b[39m: The security token included in the request is invalid. ","timestamp":"2025-01-09T00:24:38.461Z","type":"out","process_id":0,"app_name":"app"}
```

This issue was noticed when attempting to migrate the app to best practices away from long-lived credentials.

The issue appears to be due to provider-email-amazon-ses which uses nodeSES (this is still true of the latest v5), which is nearly 5 years out of date and is configured such that it won't support anything but long-lived credentials.

### Steps to reproduce the behavior

1. Setup new strapi instance in docker
2. Build container
3. Set `plugins.ts` with the below config:
```
...
export default {
	...,
	email: {
		config: {
			provider: 'amazon-ses',
			providerOptions: {
				amazon: 'https://email.ap-southeast-2.amazonaws.com',
			},
			settings: {
				defaultFrom: 'my@email.com'
			},
		},
	},
...
};

```
4. Attempt to send email

### Expected behavior

Uses environment credentials and sends email.

### Additional context

This issue was not present when providing a key and secret, but this is not best practice, and I am aware I can implement our own provider, though this issue should be fixed in the core.