fix: topologically sort CloudFormation resources before provisioning

[ctnnguyen]

Summary

Fixes #331

CloudFormationService.executeTemplate provisioned resources in JSON/YAML field iteration order with no dependency analysis. If a resource referenced another via Ref, Fn::GetAtt, or Fn::Sub, and the referenced resource appeared later in the template, the intrinsic function fell back to a literal string (e.g. CredentialsQueue.Arn instead of the actual ARN).

Adds a topological sort (Kahn's algorithm) that scans resource Properties for Ref, Fn::GetAtt, Fn::Sub variable references (including ${Resource} and ${Resource.Attr} shorthand), and explicit DependsOn declarations. Resources with false conditions are excluded from the graph. Cycles fall back to original ordering.

Type of change

• Bug fix (fix:)
• New feature (feat:)
• Breaking change (feat!: or fix!:)
• Docs / chore

AWS Compatibility

CloudFormation provisions resources respecting implicit dependencies from Ref, Fn::GetAtt, Fn::Sub, and explicit DependsOn. Without dependency ordering, templates where a resource appears before its dependency in the file would fail to resolve intrinsic functions correctly.

Checklist

• ./mvnw test passes locally
• New or updated integration test added
• Commit messages follow Conventional Commits

[hectorvent]

Thanks @ctnnguyen,

I will take a look soon.

[hectorvent]

Thanks @ctnnguyen