Replace AWS keys with IAM role

[vfalconisumo]

Purpose of this pull request

This pull request updates the production deploy workflow by replacing the AWS access/secret keys with an IAM role. The workflow needs access to AWS to allow the GitHub to trigger the site deployment pipeline in Marketing's Jenkins server.

This change in credentials was requested by IT, to follow best practices. The request is included in the Asana linked below.

The IAM role has been tested for use in the free trial deployment workflows, which mirror the workflows in this repository. Because the IAM role is only used when deploying to production, it cannot be tested with the staging environment. Therefore, I recommend this PR be merged at a time when we can immediately follow up with a PR that deploys new content, to ensure the workflow runs successfully.

The change requires a new secret, WEBOPS_AWS_ROLE_JENKINS, which has already been configured.

Once this PR is merged, the WEBOPS_AWS_ACCESS_KEY and WEBOPS_AWS_SECRET_KEY should be removed from the repo and removed from the Marketing AWS account. I'll take that action once we confirm the workflow runs successfully.

Select the type of change

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions, updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

Asana