Add aws ses send email operator.

[jmcarp]

We have an SES hook, but I don't see an SES operator yet. This patch adds the boilerplate operator to pass templated arguments through to the hook.

[github-actions]

The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Backport packages$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*.

[github-actions]

The Workflow run is cancelling this PR. Building image for the PR has been cancelled

[mik-laj]

@jmcarp What do you think to add SES support to EmailOperator?

[jmcarp]

So, write an ses email backend? That sounds reasonable. I might want to use multiple ses credentials for different tasks, so I would like this to include an optional connection argument, if that makes sense. Other email backends seem to use environment variables or special configuration variables for credentials. Any reason not to use connections instead for ses?

[mik-laj]

we don't have a lot of email backend alternatives, so we don't have good practices. if you present the implementation, I think there will be no problems to accept it.

ps. i thought to drop the use of environment variables in sendgrid backend.

[jmcarp]

Handled in another PR!