Sets cost estimation and tracking options

[TristonianJones]

Introduce library-based options for cost estimation and cost tracking

Breaking change - This change introduced a minor shift to ensure that all instances
of the interpreter.CostTracker were instantiated using interpreter.NewCostTracker().
This change revealed a bug where presence test, has(), costs were not being counted
when calling ContextEval() or Eval() with state tracking enabled. This bug has been
fixed, but revealed an inconsistency in expectations between the two method calls.

Note, these options only match against type-checked expressions. This is the
same behavior as is used internally within estimators; however, it is probably
worth indicating the cost estimates are only accurate against type-checked
expressions at a future date.

[cici37]

The cost might not set properly for other ext library as well. It might be out of scope for this PR but do we want to track it somewhere in an issue? (I am happy to create one if you are ok with it :) )

[TristonianJones]

@cici37 Yes, please, if you wouldn't mind filing an issue to introduce costs for the other extension libraries that would be great. Most of these costs are currently tracked within the K8s cost estimation extensions and should be moved back into the CEL libraries.

[cici37]

Could we merge this into 0.17 release and cut another 0.17.7 patch release for this fix? I would like to avoid bumping to 0.18 only because of the bug fix if possible. :)

[TristonianJones]

@cici37 PTAL

[cici37]

/lgtm
/approve
Thanks for helping with this!

[cici37]

/hold