fix: bump stack-config/yaml remote-state from 1.8.0 to 2.0.0

CI Lint was failing with conflicting constraints on cloudposse/utils:

    no available releases match the given constraints
    >= 1.7.1, >= 2.0.0, < 2.0.0, < 3.0.0

src/remote-state.tf (4 call sites) pinned stack-config/yaml v1.8.0,
which requires utils >= 1.7.1, < 2.0.0. CI clones aws-account-map
sibling component for ../account-map/modules/iam-roles, and
iam_roles.account_map there now uses stack-config/yaml v2.0.0, which
requires utils >= 2.0.0, < 3.0.0. The two ranges are incompatible.

Bumping all four refs to v2.0.0 aligns with the sibling component
and resolves the provider constraint. No breaking API changes
between 1.8.0 and 2.0.0 in the remote-state submodule — only the
utils version pin widens.

Author: ivan-pinatti

src/remote-state.tf

@@ -1,6 +1,6 @@
 module "vpc" {
   source  = "cloudposse/stack-config/yaml//modules/remote-state"
-  version = "1.8.0"
+  version = "2.0.0"
 
   component = var.vpc_component_name
 
@@ -9,7 +9,7 @@ module "vpc" {
 
 module "vpc_ingress" {
   source  = "cloudposse/stack-config/yaml//modules/remote-state"
-  version = "1.8.0"
+  version = "2.0.0"
 
   for_each = {
     for i, account in var.allow_ingress_from_vpc_accounts :
@@ -27,7 +27,7 @@ module "vpc_ingress" {
 
 module "eks" {
   source  = "cloudposse/stack-config/yaml//modules/remote-state"
-  version = "1.8.0"
+  version = "2.0.0"
 
   for_each  = local.eks_security_group_enabled ? var.eks_component_names : toset([])
   component = each.value
@@ -38,7 +38,7 @@ module "eks" {
 
 module "dns_gbl_delegated" {
   source  = "cloudposse/stack-config/yaml//modules/remote-state"
-  version = "1.8.0"
+  version = "2.0.0"
 
   component   = "dns-delegated"
   environment = var.dns_gbl_delegated_environment_name