chore: update remote-state to 2.0.0 and switch to standalone account-map (#84)

* chore: update remote-state to 2.0.0 and vendor account-map from standalone repo

- Update remote-state module from 1.8.0 to 2.0.0
- Switch vendor.yaml account-map source from monorepo to standalone
  cloudposse-terraform-components/aws-account-map at v1.537.2

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* revert: keep remote-state at 1.8.0 for now

Utils provider v2.x changes workspace name resolution in
utils_component_config, breaking the vpc-flow-logs-bucket remote-state
lookup in tests. VPC doesn't directly declare a utils provider, so
keeping remote-state at 1.8.0 avoids the conflict while the workspace
resolution change is investigated.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* revert: restore remote-state to 2.0.0

The workspace resolution issue with utils v2.x needs to be
investigated, but reverting to 1.8.0 would reintroduce the
utils provider constraint conflict.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* chore: bump vpc-flow-logs-bucket vendor to v1.537.0

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* remove environment

* fix: remove Go templates from test backend config

Utils provider v2.1.0+ no longer resolves Go templates in
utils_component_config output (disabled to fix ETXTBSY crash with
!terraform.output YAML tags). This caused terraform_remote_state
to receive literal {{ .component }} template strings as paths,
failing to find state files.

Use a single state directory and rely on terraform workspace
isolation to separate state per component.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* revert: restore Go templates in test backend config

The {{ .component }} pattern is standard across all component test
fixtures. The fix for template resolution needs to be upstream in the
utils provider — it should selectively re-enable template processing
for backend config while still disabling !terraform.output YAML
functions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* remove backend config

* use defaults

* revert changes

* cleanup

* revert some files to main

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Benbentwo

src/remote-state.tf

@@ -2,7 +2,7 @@ module "vpc_flow_logs_bucket" {
   count = local.vpc_flow_logs_enabled ? 1 : 0
 
   source  = "cloudposse/stack-config/yaml//modules/remote-state"
-  version = "1.8.0"
+  version = "2.0.0"
 
   component   = var.vpc_flow_logs_bucket_component_name
   environment = var.vpc_flow_logs_bucket_environment_name

test/fixtures/vendor.yaml

@@ -6,8 +6,8 @@ metadata:
 spec:
   sources:
     - component: "account-map"
-      source: github.com/cloudposse/terraform-aws-components.git//modules/account-map?ref={{.Version}}
-      version: 1.520.0
+      source: github.com/cloudposse-terraform-components/aws-account-map.git//src?ref={{.Version}}
+      version: v1.537.2
       targets:
         - "components/terraform/account-map"
       included_paths:
@@ -19,7 +19,7 @@ spec:
 
     - component: "vpc-flow-logs-bucket"
       source: github.com/cloudposse-terraform-components/aws-vpc-flow-logs-bucket.git//src?ref={{.Version}}
-      version: v1.534.0
+      version: v1.537.0
       targets:
         - "components/terraform/vpc-flow-logs-bucket"
       included_paths: