Notify teams of AB tests close to expiry

[cemms1]

What does this change?

Adds a scheduled lambda for the new AB testing framework to notify teams of upcoming AB test expiry dates or to let them know that tests have already expired.

• The lambda is scheduled to run at 5am every weekday for PROD but not for CODE, though in both environments it can be triggered manually
• It fetches active AB tests (those switched "ON" in the code) and filters by those within 2 days of expiry or which have already expired
• It then gets a unique list of AB test owners for those tests and creates three lists of tests for each owner:
  • Expired tests
  • Tests expiring today at midnight
  • Tests expiring tomorrow at midnight
• For each owner of an AB test close to expiry, it sends an email using SES with a breakdown of their expiring tests in tabular format

Example email format

Tested in CODE

Why?

We want to make sure expired tests are turned off and/or removed from the codebase if no longer active. Notifying teams of this helps to keep them aware of this.

[github-actions]

Deploy build 361 of dotcom:ab-testing to CODE

All deployment options

• Deploy build 361 of dotcom:ab-testing to CODE
• Deploy parts of build 361 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Deploy build 23514 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 23514 of dotcom:rendering-all to CODE
• Deploy parts of build 23514 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.