DDLS-408 add encryption to remaining dynamo table

[jamesrwarren]

Purpose

This adds the encrypting to the ramaining dynamodb resource.

Fixes DDLS-408

Approach

Added the encryption. Additionally, I have created two new security groups instead of just amending the current ones. I'm doing it this way to avoid any down time. In subsequent PRs I will duplicate the settings for the cache sg for all the env services then in another PR remove the original. This will result in zero downtime. It's a bit more of a faff but I'll just add it to other PRs that I do.

Learning

NA

Checklist

• I have performed a self-review of my own code
• I have updated documentation (Confluence/ADR/tech debt doc) where relevant
• I have added tests to prove my work
• The product team have approved these changes
• I have checked my work for potential security issues and refered to the OWASP top 10

Frontend

• I have run an in-browser accessibility test (e.g. WAVE, Lighthouse)
• There are no deprecated CSS classes noted in the profiler
• Translations are used and the profiler doesn't identify any missing
• Any links or buttons added are screen reader friendly and contextually complete
• If adding GA events, I have updated or checked the existing category or label values