Conditional policy evaluating incorrectly: second policy in policy chain always triggers

Current behaviour

When creating a conditional policy with two policies in the chain, the second policy always fires

Expected behaviour

Policies in the conditional policies policy chain should only fire if the conditional policies conditions are met

For example, we see the following in the logs when the conditional policy has the headers and camel policies in it's chain and no default proxies configured:
<...>
2023/02/22 00:01:01 [debug] 01#01: *123 conditional.lua:69: Condition not met in conditional policy, requestID=aaabbbccc111222333
<...>
2023/02/22 00:01:01 [debug] 01#01: *123 upstream.lua:228: call(): using proxy: http://camel-proxy.example.com:8080, requestID=aaabbbccc111222333 <...>