Upgrade to node v24 (#437)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated Node.js runtime from version 22.x to 24.x across Lambda
functions and build environments.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: devksingh4

Makefile

@@ -32,13 +32,13 @@ build: src/
 	make build_swagger
 	cp -r src/api/resources/ dist/api/resources
 	rm -rf dist/lambda/sqs
-	docker run --rm -v "$(shell pwd)/dist/lambda":/var/task public.ecr.aws/sam/build-nodejs22.x:latest \
+	docker run --rm -v "$(shell pwd)/dist/lambda":/var/task public.ecr.aws/sam/build-nodejs24.x:latest \
 	sh -c "npm i -g yarn && $(yarn_env) yarn $(yarn_install_params) && \
 			rm -rf node_modules/aws-crt/dist/bin/{darwin*,linux-x64*,linux-arm64-musl} && \
 			rm -rf node_modules/argon2/prebuilds/{darwin*,freebsd*,linux-arm,linux-x64*,win32-x64*} && \
 			rm -rf node_modules/argon2/prebuilds/linux-arm64/argon2.armv8.musl.node"
 
-	docker run --rm -v "$(shell pwd)/dist/sqsConsumer":/var/task public.ecr.aws/sam/build-nodejs22.x:latest \
+	docker run --rm -v "$(shell pwd)/dist/sqsConsumer":/var/task public.ecr.aws/sam/build-nodejs24.x:latest \
 	sh -c "npm i -g yarn && $(yarn_env) yarn $(yarn_install_params) && \
 				rm -rf node_modules/aws-crt/dist/bin/{darwin*,linux-x64*,linux-arm64-musl} && \
 				rm -rf node_modules/argon2/prebuilds/{darwin*,freebsd*,linux-arm,linux-x64*,win32-x64*} && \

terraform/modules/archival/main.tf

@@ -305,7 +305,7 @@ resource "aws_lambda_function" "api_lambda" {
   role             = aws_iam_role.archive_role.arn
   architectures    = ["arm64"]
   handler          = "dynamoStream.handler"
-  runtime          = "nodejs22.x"
+  runtime          = "nodejs24.x"
   filename         = data.archive_file.api_lambda_code.output_path
   timeout          = 90
   memory_size      = 512

terraform/modules/lambdas/main.tf

@@ -351,7 +351,7 @@ resource "aws_lambda_function" "api_lambda" {
   role             = aws_iam_role.api_role.arn
   architectures    = ["arm64"]
   handler          = "lambda.handler"
-  runtime          = "nodejs22.x"
+  runtime          = "nodejs24.x"
   filename         = data.archive_file.api_lambda_code.output_path
   timeout          = 15
   memory_size      = 2048
@@ -380,7 +380,7 @@ resource "aws_lambda_function" "sqs_lambda" {
   role             = aws_iam_role.sqs_consumer_role.arn
   architectures    = ["arm64"]
   handler          = "index.handler"
-  runtime          = "nodejs22.x"
+  runtime          = "nodejs24.x"
   filename         = data.archive_file.sqs_lambda_code.output_path
   timeout          = 300
   memory_size      = 2048
@@ -411,7 +411,7 @@ resource "aws_lambda_function" "hicpu_lambda" {
   role             = aws_iam_role.api_role.arn
   architectures    = ["arm64"]
   handler          = "lambda.handler"
-  runtime          = "nodejs22.x"
+  runtime          = "nodejs24.x"
   filename         = data.archive_file.api_lambda_code.output_path
   timeout          = 15
   memory_size      = 4096 // This will get us 2 full CPU cores, which will speed up those cryptographic ops that require this server
@@ -510,7 +510,7 @@ resource "aws_lambda_function" "linkry_edge" {
   function_name    = "${var.ProjectId}-linkry-edge"
   role             = aws_iam_role.linkry_lambda_edge_role[0].arn
   handler          = "index.handler"
-  runtime          = "nodejs22.x"
+  runtime          = "nodejs24.x"
   publish          = true
   timeout          = 5
   memory_size      = 128