fix: added missing launch template tag_specifications (#4544)

copy from #4531

Currently the launch template specification adds tags only on resource
types of `instance` and `volume` this leaves the other 2 supported
resource types (`spot-instances-request` and `network-interface`)
untagged which by extensions does not produce accurate data on Cost
Explorer.

This pr fixes this by adding the missing `tag_specifications`
configurations.

---------

Co-authored-by: konkerama <konkeramaris@gmail.com>

Author: npalm

modules/runners/main.tf

@@ -206,6 +206,34 @@ resource "aws_launch_template" "runner" {
     )
   }
 
+  tag_specifications {
+    resource_type = "spot-instances-request"
+    tags = merge(
+      local.tags,
+      {
+        "Name" = format("%s", local.name_runner)
+      },
+      {
+        "ghr:runner_name_prefix" = var.runner_name_prefix
+      },
+      var.runner_ec2_tags
+    )
+  }
+
+  tag_specifications {
+    resource_type = "network-interface"
+    tags = merge(
+      local.tags,
+      {
+        "Name" = format("%s", local.name_runner)
+      },
+      {
+        "ghr:runner_name_prefix" = var.runner_name_prefix
+      },
+      var.runner_ec2_tags
+    )
+  }
+
   user_data = var.runner_os == "windows" ? base64encode(local.user_data) : base64gzip(local.user_data)
 
   tags = local.tags

modules/runners/pool/main.tf

@@ -189,7 +189,7 @@ resource "aws_iam_role" "scheduler" {
   permissions_boundary = var.config.role_permissions_boundary
 
   assume_role_policy = data.aws_iam_policy_document.scheduler_assume.json
-  tags = var.config.tags
+  tags               = var.config.tags
 }
 
 resource "aws_iam_role_policy" "scheduler" {