v2.2.0

feat: expose lambda_architectures and forwarder_use_cache_bucket @johncblandii (#109)

## Summary

• Pass lambda_architectures and forwarder_use_cache_bucket through to the upstream cloudposse/datadog-lambda-forwarder/aws module (pinned at 1.10.1), and add matching wrapper variables.
• Enables consumers to run Datadog Forwarder 5.x artifacts by setting lambda_architectures = ["arm64"]. Those artifacts ship native dependencies built for arm64 and fail on x86_64 during cold start with errors such as Runtime.ImportModuleError: No module named 'ujson', which silently stops CloudWatch logs from reaching Datadog.
• Lets a stack explicitly control the forwarder cache bucket via forwarder_use_cache_bucket (default true, preserving upstream behavior).

Changes

• src/main.tf: forward lambda_architectures and forwarder_use_cache_bucket to the upstream module. (lambda_runtime was already wired through.)
• src/variables.tf:
  • lambda_architectures — list(string), default null (no change until a stack opts in).
  • forwarder_use_cache_bucket — bool, default true (matches upstream default).
• README.md / src/README.md: regenerated Inputs tables to document the new variables.

Testing

• terraform fmt -check -recursive — clean
• terraform validate — Success (only pre-existing, unrelated datadog_integration_aws_lambda_arn deprecation warnings)
• Verified both variables exist with matching type/default in upstream module 1.10.1

Notes

• Both defaults are chosen to be no-ops, so existing stacks are unaffected until they explicitly set the new variables.
• Upstreams wrapper changes originally made downstream by Prezzee.

Summary by CodeRabbit

• New Features

  • Added support for configuring Lambda architecture options.
  • Added a new setting to enable or disable use of a cache bucket.

• Documentation

  • Updated the setup docs with the latest supported provider version.
  • Documented the new configuration options and their defaults.