Refactor Lambda Function to Use lambdaInvoke Instead of HTTP Requests

[lakshayman]

Issue Description

The current implementation of the Lambda function utilizes HTTP requests to call other Lambda functions instead of using the more efficient lambdaInvoke method.

Expected Behavior

The function should invoke other Lambda functions directly using the lambdaInvoke method, which would improve performance and reduce latency compared to making HTTP requests.

Current Behavior

Currently, the function makes HTTP POST requests to other Lambda functions, which can lead to increased response times and potential failure scenarios if the HTTP endpoint is not reachable.

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

1. Deploy the current Lambda function.
2. Trigger the function and observe the behavior of the profile calling process via HTTP requests.

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

Switching from HTTP requests to the lambdaInvoke method will require changes to the code to utilize the AWS SDK for Go to invoke the functions directly.

Checklist

• I have read and followed the project's code of conduct.
• I have searched for similar issues before creating this one.
• I have provided all the necessary information to understand and reproduce the issue.
• I am willing to contribute to the resolution of this issue.