Aws-syndicate

- Added support lambda layers with runtime DotNet
- Tagging added to `oas_v3 openapi` API Gateway.
- SNS topic deletion fixed.
- Added an example of a lambda function with runtime `dotnet`
- Fixed silent overwriting existing lambda with runtime Java during the command `syndicate generate lambda`

- Changed deployment flow to work despite the latest deployment failed
- Changed deployment flow with the flag `--continue_deploy` to work despite the latest deployment being absent or succeeded
- Implemented rolling back on error mechanism(flag `--rollback_on_error`) for deployment flow with the flag `--continue_deploy`
- Added support of lambda functions with runtime DotNet
- Added possibility to deploy/update resource-specific tags
- Added confirmation request mechanism for the `update` command in case the latest deployment failed
- Added the flag `--force` for the `update` command to run an update without confirmation request in case the latest deployment failed
- Added proper messages for commands `update` and `clean` if deployed resources are absent(output file not found)
- Added logging of resource names that cause errors to improve error diagnostics
- Added enhanced logging of the `build` command execution
- Added validation for existence of bundle and deploy names
- Added validation for incompatible parameters(`--events`, `--resources`) of the command `syndicate status`
- Added the possibility to add resource-specific tags via the resource meta generation(flag `--tags`)
- Added tags support to the Syndicate Java plugin. The `Tags` and the `Tag` annotations added to the plugin. The Java plugin version updated to 1.14.0
- Changed the Java lambda template to use the Syndicate Java plugin version 1.14.0 for the new lambda generation.
- Event status added to the command `syndicate status` output
- Reworked lambda triggers update to compare local event sources meta with the previous remote one
- Reworked lambda triggers deletion to not list every resource of the trigger type to remove it from lambda (**EPMCEOOS-6112**)
- The key `operation_status` in `latest_deploy` section of the syndicate state file(.syndicate) renamed to `is_succeeded`
- Fixed lock resolving issue
- Fixed an issue related to bucket name resolving in the s3_bucket policy
- Added logging of resource names that cause errors to improve error diagnostics
- Fix the resource update issue that occurs when a deploy_name is specified by user (not default one) but deployment
output for the latest deployment is empty
- Fixed an issue where updating only certain resources caused the deployment output to be overwritten with only these
resources, instead of updating the existing meta
- Fixed deployment failure if resource name is the same as resource type
- Fixed an issue related to resource name resolving if ARN is a list item
- Fixed an issue related to name resolving if one resource name contains another resource name
- Fixed an issue when a lambda deployment fails when a trigger defined in meta does not exist
- Fixed an issue related to updating lambda triggers
- Fixed lambda event source mapping inactivity after deployment
- Improved logging for the deletion of a resource that does not exist in the account
- Improved logging in case of the absence of resources to clean
- Fixed Lambda Layer packaging for the NodeJS runtime
- Fixed an issue where newly added resources (after deploy) were causing the update operation to fail
- Fixed a synchronization issue that prevented the batch job queue from being deleted before its state was fully updated
- Fixed an issue related to removing CloudWatch alarms that were used for Dynamodb autoscaling
- Fixed an issue with the absence of lambda's information in the output file in case deployment failed on the trigger configuration step
- Fixed an issue related to losing state after partial clean
- Fixed an issue related to the latest output resolving
- Fixed an issue related to the API Gateway throttling and cache configuration for ANY method
- Fixed an issue with `--force_upload` being required while syndicate assemble

- Speed up deletion of s3 bucket with lots of objects

- Added possibility to configure `FunctionResponseTypes` for lambda functions
- Updated maven plugin version to 1.12.0 with support of `FunctionResponseTypes`
- Added possibility to set up Cognito user pool ID in lambda function environment variable
- Added possibility to set up Cognito user pool client ID in lambda function environment variable
- Fix lambda triggers deletion when removed from meta
- Fix resources dependencies resolving
- Fix losing successfully deployed resources from the output file during deployment with the option `--continue_deploy`
- Fix API Gateway duplication in case of existing API Gateway with the same name
- Fix detection of usage `--rollback_on_error` option with an incompatible option `--continue_deploy`
- Changed datetime format for lock attributes in the `.syndicate` file to UTC format
- The Syndicate Java plugin version updated to 1.13.0 with changes:
- The ResourceType enum for the DependsOn annotation extended with new type ResourceType.COGNITO_USER_POOL
- The EnvironmentVariable annotation for the Syndicate Java plugin improved to support the value transformer
- A new value transformer type created ValueTransformer.USER_POOL_NAME_TO_USER_POOL_ID
- A new value transformer type created ValueTransformer.USER_POOL_NAME_TO_CLIENT_ID
- The generate Java lambda template changed to use the Syndicate Java plugin version 1.13.0

- Added ability for `clean` command to automatically resolve if `--rollback` is needed.
- Fixed an issue related to `log group already exists` error while deploying or updating `lambda`.
- Updated `syndicate deploy --continue_deploy` command, now it can save output and actually continue deployment resources.
- Implemented `rollback_on_error` flag for `syndicate deploy` command. Is flag is `True`, all resources that have been deployed during deployment process, would be cleaned.
- Fixed an issue related to deploying multiple resources with same type, now it catches an `Exception` in case of a deployment error of one of the resources and returns it along with the outputs.
- Fixed `deploy` command responses.
- Added support of Python 3.12
- Fixed an issue related to ARNs resolving in case of empty resource name
- Fixed an issue related to improper filtering of resources in case of different types of filter usage
- Fixed an error related to SQS FIFO Queue availability regions
- Fixed an issue related to deploying SQS Queue with configured redrive_policy
- Fixed an issue when only the last s3 trigger was configured for the lambda
- Added `force_upload` action to all assemble commands

- Added support of custom authorizer names in Open API specification security schemes
- Fixed quietness of errors while deploying/updating API Gateway via OpenAPI specification
- Fixed API GW deletion when openapi specification is invalid
- Fixed issue with the command `generate meta api_gateway_resource`
- Fixed lambda function deployment fails in case of matching any resource name with prefix or/and suffix