Fix ses smtp accesskey

[alexinthesky]

Description of your changes

re-add region to aws_iam_access_key
Fixes #717

I have:

• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

[turkenh]

Thank you for your contribution @alexinthesky 🙌

[turkenf]

/test-examples="examples/iam/user.yaml"

[turkenh]

Hmm, this would indeed be a breaking change for IAM AccessKey resource users since their existing resource will start failing with the lack of region parameter.

I think we would also need to add it as optional instead of required.

[turkenf]

Hi, @alexinthesky are you still interested in moving this PR forward?

[turkenf]

@alexinthesky, I'm closing this PR for now, if you're still interested and want to move it forward, feel free to reopen it.

[tdjordan]

I am running into a situation where I want to create an AccessKey for a User but get the ses_smtp_password_v4 for a different region than what is generated by default.

For example, the ses_smtp_password_v4 for us-west-2 instead of the currently generated one for us-east-2.

I am interested in re-opening this PR to allow the region to be specified for the aws_iam_access_key resource.

What is needed for me to do to help drive this PR into an acceptable merge state?

I have little experience in go but am willing to learn and facilitate.

Alternatively, I have looked at the surrounding code and it is currently unclear to me what is populating the Region in the AWSCLient context. Could someone point me in the right direction?