release 0.64.5

[sastels]

What are you changing?

• Releasing a new version of Notify
• Changing kubernetes configuration

Provide some background on the changes

basically, bump up CWAgent memory and use imdsv1 on the spot instances

• feat: Celery email send pods in staging #2118
• Revert "feat: Celery email send pods in staging" #2122
• Revert "Revert "feat: Celery email send pods in staging"" #2124
• fix: Setting higher memory limits in cwagent #2125
• Setting http tokens to optional which should enable imdsv1  #2127
• Karpenter spot instances on imdsv1, celery back on spot #2128

If you are releasing a new version of Notify, what components are you updating

• API
• Admin
• Documentation
• Document download API

Checklist if releasing new version:

• I made sure that the changes are as expected in Notify staging
• I have checked if the docker images I am referencing exist
  • api lambda (requires Notification-Production / AdministratorAccess login)
  • api k8s
  • admin
  • documentation
  • document download API

Checklist if making changes to Kubernetes:

• I know how to get kubectl credentials in case it catches on fire

After merging this PR

• I have verified that the tests / deployment actions succeeded
• I have verified that any affected pods were restarted successfully
• I have verified that I can still log into Notify production
• I have verified that the smoke tests still pass on production
• I have communicated the release in the #notify Slack channel.