Fix Caching of Clients in Lambda

[JNygaard-Skylight]

Describe the bug
We had initially decided that clients (S3, auth, OpenSearch) should be cached so that they persist over lambda runs. This is not happening. Instead they get initialized twice. Once at the beginning of lambda function, and once again when they are used. Compared to the rest of the code the initilizaing of these clients is pretty quick so it may be most prudent to simply remove this faulty logic. However if it would not take too much effort there is nothing in wrong with caching elements that are consistent across runs.

Impact
Please describe the impact this bug is causing to your program or organization.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Logs
If applicable, please attach logs to help describe your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[bamader]

@JNygaard-Skylight I might be looking in the wrong place, but I'm not actually seeing the duplication in the code. From what I can tell, we initialize e.g. the aws_auth and the S3_auth separately in the Index Lambda and the TTC Lambda Function, but that should be desired behavior since the two are separate Lambdas altogether. In lines 65-76 of lambda_function.py, it looks like we check if the auth already exists in the cache before initializing it, and then nowhere else in the file do we touch the auth. Am I missing something here? Or was there another place you were looking?