Ds allow caa failure flag and set http timeout

[sciros]

This pull request introduces improvements to the configuration and environment handling for the AWS Lambda functions, updates dependencies, and enhances integration test coverage and diagnostics. The main changes include adding support for new timeout configuration options, refactoring environment variable injection to reduce duplication, and updating dependencies for better compatibility and features. The integration tests have also been expanded and improved for better reliability and debugging.

Configuration and Environment Handling:

• Added support for new timeout configuration options (http-client-timeout-seconds, dns-timeout-seconds, dns-resolution-lifetime-seconds) in config.example.yaml, and ensured these are injected into the Lambda environment via Terraform templates (aws-perspective.tf.template). [1] [2] [3]
• Refactored environment variable injection in configure.py by introducing the set_common_env_configuration helper, reducing code duplication and making it easier to add new environment variables. [1] [2] [3]

Lambda Function Initialization:

• Updated MpicDcvCheckerLambdaHandler and MpicCaaCheckerLambdaHandler to read new timeout environment variables and pass them to their respective checker classes, improving configurability and robustness. [1] [2]

Dependency and Version Updates:

• Updated dependencies in pyproject.toml (aiohttp, open-mpic-core) and bumped the API spec version and package version for compatibility and feature improvements. [1] [2] [3]

Integration Test Improvements:

• Enhanced integration tests in test_deployed_mpic_api.py to print responses when assertions fail, aiding debugging. Added a new test to check behavior when CAA lookup failures are allowed, and improved assertion placement for clarity. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Minor Documentation and Configuration Changes:

• Updated the README.md to clarify the order of deployment commands for DNSSEC and non-DNSSEC options.
• Changed the default AWS region in example configuration to us-east-2.

[birgelee]

1. why is the example config us-west-1 changed to us-east-2?
2. README.md contains a permalink to the spec version (for better or for worse). This needs to be updated to the proper commit for 3.6.0

[sciros]

1. why is the example config us-west-1 changed to us-east-2?
2. README.md contains a permalink to the spec version (for better or for worse). This needs to be updated to the proper commit for 3.6.0

The first one wasn't intended, will revert. (I think we had the Coordinator in us-east-2 the whole time and I thought why have it live alone.. but I forgot you updated the example to match MPIC Labs config.) Will update README as well.

[birgelee]

Looks good.