Pull request intervention for infrastructure-as-code risks with Bitbucket custom merge checks

This post introduces a new capability for Bitbucket custom merge checks, leveraging the Forge ecosystem and React to intervene on pull requests. It details a four-phase framework for detecting 'Known Risks' in infrastructure-as-code changes, specifically focusing on service descriptors. The framework involves inspecting pull requests for files of interest (e.g., *.sd.yaml), evaluating changes against known risk patterns (e.g., DynamoDB, RDS), reporting detected issues with guidance, and requiring user submission approval with monitoring and rollback criteria. This enhances the existing Merge Queues feature by adding a pre-merge gate for infrastructure-related risks.