Update cost model and cost tracker logic when runtime starts to consume CU for all builtins

[tao-stones]

Problem

feature gate native_programs_consume_cu (#30620) changes how builtins consume compute units:

feature gate status	builtins consume CU (Y/N)	compute_budget_compute_unit_limit applies to
not activated (now)	No	BPF programs only
activated	Yes	both BPF and Builtin programs

This change requires cost model and cost tracker logic to be updated accordingly.

Summary of Changes

1. cost_model: after feature gate is enabled. compute_unit_limit would apply to both builtin and bpf programs in get_transaction_cost().
2. cost_tracker: when update with "actual consumed CUs", with feature gate enabled, it shall count builtin cost as part of "actual consumed CUs"
3. add method programs_execution_cost() to TransactionCost to combine builtin and bpf execution costs
4. updated tests to cover feature gate native_programs_consume_cu status

Note: behind feature gate #30620

[codecov]

Codecov Report

Attention: Patch coverage is 99.68553% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 81.9%. Comparing base (1bc1012) to head (8841096).
Report is 1865 commits behind head on master.

❗ Current head 8841096 differs from pull request most recent head 31c2018. Consider uploading reports for the commit 31c2018 to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #32080     +/-   ##
=========================================
- Coverage    82.0%    81.9%   -0.1%     
=========================================
  Files         769      765      -4     
  Lines      208993   208735    -258     
=========================================
- Hits       171390   171112    -278     
- Misses      37603    37623     +20     

[apfitzge]

is default() all disabled? this seems like we're testing more than 1 feature at a time.

[tao-stones]

All features are disabled by default(). Yea, the point is valid. I did this because it's easy and (looks) clean - it tests two status: all on or all off, but that may have added ambiguity

[apfitzge]

Yeah testing features is unfortunately kind of messy, particularly if we've got multiple "in flight" features in a single component such as cost model

[willhickey]

This repository is no longer in use. Please re-open this pull request in the agave repo: https://github.com/anza-xyz/agave