Improve scenario-aware validation and resolved-value handling

[satyakigh]

Summary

Improve condition-aware CloudFormation validation by expanding resolved values into bounded, compatible scenarios and applying that model consistently across IAM policies, lifecycle attributes, schema validation, and route-table identity checks.

Changes

• Expand conditional maps, lists, and enum variants into compatible scenarios while preserving condition assumptions and authored source paths.
• Enforce per-value and global scenario budgets, make global accounting safe for concurrent queries, and emit I9052 when analysis is curtailed.
• Materialize IAM identity-policy documents per reachable scenario, including AWS::NoValue pruning, Fn::Sub handling, and branch-qualified diagnostic locations shared by Rego and CEL.
• Track effective lifecycle-attribute presence and invalid values for condition-aware CreationPolicy and UpdatePolicy validation, including E3016 registration.
• Improve parameter-default validation, including CommaDelimitedList defaults.
• Extend schema-composition checks across reachable property scenarios, including required-property groups and notEnum handling.
• Count Unicode scalar values rather than UTF-8 bytes for string-length diagnostics.
• Add resolved-value identity support for route-table association conflict detection.