Preserve source information during CEL policy composition. (#1253)

* Preserve source information during policy composition.

The old implementation outputs the wrong source information for policy files derived from the dummy AST created by RuleComposer.Compose. This change fixes that by preserving the correct source and merging the offset ranges of the rule match expressions inserted by the composer optimizer into the final AST.

* Fix source info for relative sources.

Support unwrapping unknown implementations of `proto.Message` (#1207)

* Support unwrapping unknown implementations of `proto.Message`

Signed-off-by: Sri Krishna <skrishna@buf.build>

* Add test case

Signed-off-by: Sri Krishna <skrishna@buf.build>

---------

Signed-off-by: Sri Krishna <skrishna@buf.build>
Co-authored-by: Sri Krishna <skrishna@buf.build>

Cost tracking for list operations (#1192)

Cost tracking for list operations (#1192)

Refactoring changes to create a test runner option from passed flags,…

… correct indentation and add package level comment for test (#1165)

* corrected indentation and added package comment for /test
* fix indentation for required_labels test file
* added test runner options from flags as a public method

Separate unnest optimization from composer to capture type info (#1138)

* Separate unnest optimization from composer to capture type info
* Simplify the variable tracking during unnest

Support for splitting nested branching operators within policies (#1136)

* Support for splitting nested branching operators within policies
* Introduce an ast.Heights() helper
* Updated tests and expanded flattening to all calls
* Added test case for comprehension pruning during unnest

Support for feature flags and validators in env.Config (#1132)

* Support for feature flags and validators in env.Config
* Minor update to documentation

Add k8s custom policy tag handler for test (#1121)

* Add k8s custom policy tag handler for test
* Add copyright and remove redundant attribute from go_library target

Minor update on cost order (#1119)

* slight reordering in cost computation to preserve legacy compatibility
* Additional tests to attempt to catch ordering issues with cost estimation