Fix: Use Lambda URL to bypass Gateway timeout limit

[LeeXuanHua]

Summary

Fixed AWS API Gateway timeout limit for AWS Lambda deployment, by replacing API Gateway with Lambda function URL to generate invocation URL

Problem: Previous deployment with API Gateway (with differing page paths for each Lambda function) can only handle invocations within 29 seconds due to gateway timeout. However, actual traces involve invocations longer than 29s. Although our current code filters for invocations under 1 minute, it is not sufficient to address the problem.

**Included minor fixes to improve the logging description of errors.

Implementation Notes ⚒️

Solution: Utilise AWS' Lambda function URL feature to increase the maximum invocation duration to 15 minutes (same as Lambda execution timeout limit).

Therefore, program can now handle any requestedDuration within 15 minutes and the resulting function URLs no longer share the same domain name (unlike previous approach where different Lambda functions share the same domain name due to usage of an API Gateway and only differ for the page path)

External Dependencies 🍀

• Relies on Serverless.com framework for deployment, and that resulting function URLs are displayed in console/terminal in sequence (to map the function URL to the correct Lambda function)

Breaking API Changes ⚠️

• N/A

[LeeXuanHua]

@cvetkovic, could you help to review the above changes, thanks!