Combine builtin and BPF compute cost in cost model

[tao-stones]

Problem

feature gate solana-labs#30620 has been activated everywhere, SVM now consumes compute units uniformly for both builtins and BPF instructions. Cost Model should no longer estimate their cost separately.

Original PR: solana-labs#32080

Summary of Changes

• combine builtin and bpf cost into programs_execution_cost, update metrics reporting as well.
• update tests

Fixes #

[codecov-commenter]

Codecov Report

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

Project coverage is 81.8%. Comparing base (3f9a7a5) to head (79a31b9).
Report is 8 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master      #29     +/-   ##
=========================================
- Coverage    81.8%    81.8%   -0.1%     
=========================================
  Files         837      838      +1     
  Lines      225922   225939     +17     
=========================================
- Hits       184955   184913     -42     
- Misses      40967    41026     +59     

[apfitzge]

lgtm

[mergify]

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.