[PRMP-620] bump up nodejs and packages version

[joefong-nhs]

• bump up nodejs version to 22.5
• bump up packages version to address audit alerts
• fix an issue caused by using newer version of Axios (header silently ignored if the value is boolean false, see Axios removes false values from headers axios/axios#6013 (comment))

[chrisbloe-nhse]

All of these changes are looking good and match those we've seen on ehr-out.

[chrisbloe-nhse]

All of these changes are looking good and match those we've seen on ehr-out.

Just one comment to review.

[github-actions]

Report for environment: pre-prod

Terraform Format and Style 🖌success

Format Output

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.61.0...
- Installed hashicorp/aws v5.61.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan (0 to add, 1 to change, 0 to destroy)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_cloudwatch_log_metric_filter.log_metric_filter will be updated in-place
  ~ resource "aws_cloudwatch_log_metric_filter" "log_metric_filter" {
        id             = "pre-prod-gp2gp-messenger-error-logs"
        name           = "pre-prod-gp2gp-messenger-error-logs"
        # (2 unchanged attributes hidden)

      ~ metric_transformation {
            name          = "ErrorCountInLogs"
          + unit          = "None"
            # (4 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

[github-actions]

Report for environment: dev

Terraform Format and Style 🖌success

Format Output

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.61.0...
- Installed hashicorp/aws v5.61.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan (0 to add, 1 to change, 0 to destroy)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_cloudwatch_log_metric_filter.log_metric_filter will be updated in-place
  ~ resource "aws_cloudwatch_log_metric_filter" "log_metric_filter" {
        id             = "dev-gp2gp-messenger-error-logs"
        name           = "dev-gp2gp-messenger-error-logs"
        # (2 unchanged attributes hidden)

      ~ metric_transformation {
            name          = "ErrorCountInLogs"
          + unit          = "None"
            # (4 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

[github-actions]

Report for environment: prod

Terraform Format and Style 🖌success

Format Output

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.61.0...
- Installed hashicorp/aws v5.61.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan (0 to add, 2 to change, 0 to destroy)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_cloudwatch_log_metric_filter.log_metric_filter will be updated in-place
  ~ resource "aws_cloudwatch_log_metric_filter" "log_metric_filter" {
        id             = "prod-gp2gp-messenger-error-logs"
        name           = "prod-gp2gp-messenger-error-logs"
        # (2 unchanged attributes hidden)

      ~ metric_transformation {
            name          = "ErrorCountInLogs"
          + unit          = "None"
            # (4 unchanged attributes hidden)
        }
    }

  # aws_security_group.gocd_to_gp2gp_messenger will be updated in-place
  ~ resource "aws_security_group" "gocd_to_gp2gp_messenger" {
        id                     = "sg-00f65bbf8a539d6f8"
      ~ ingress                = (sensitive value)
        name                   = "prod-gocd-to-gp2gp-messenger"
        tags                   = {
            "CreatedBy"   = "prm-deductions-gp2gp-messenger"
            "Environment" = "prod"
            "Name"        = "prod-gocd-to-gp2gp-messenger-sg"
        }
        # (8 unchanged attributes hidden)
    }

Plan: 0 to add, 2 to change, 0 to destroy.

[github-actions]

Report for environment: test

Terraform Format and Style 🖌success

Format Output

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.61.0...
- Installed hashicorp/aws v5.61.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan (0 to add, 1 to change, 0 to destroy)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_cloudwatch_log_metric_filter.log_metric_filter will be updated in-place
  ~ resource "aws_cloudwatch_log_metric_filter" "log_metric_filter" {
        id             = "test-gp2gp-messenger-error-logs"
        name           = "test-gp2gp-messenger-error-logs"
        # (2 unchanged attributes hidden)

      ~ metric_transformation {
            name          = "ErrorCountInLogs"
          + unit          = "None"
            # (4 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.