Fix reserve minimal compute units for builtins

[tao-stones]

Problem

Implementing solana-foundation/solana-improvement-documents#170 by defining MAX_BUILTIN_ALLOCATION_COMPUTE_UNIT_LIMIT to 3K CUs, then use it to allocate builtin instructions' CU Meters for VM and cost tracking for leaders.

Summary of Changes

• Resolve if builtin program has been migrated to core bpf by check feature status
• When calculates default tx cu limits, use MAX_BUILTIN_ALLOCATION_COMPUTE_UNIT_LIMIT per builtin instruction, including compute-budget program instructions.
• Cost model reads cu limits from RuntimeTransaction's static_meta, replacing a localized implementation that isn't consistent with compute-budget.
• Changes are behind Feature gate
• updated existing tests to allow additional feature_set parameters (touch many files)
• add final tests to verify new behavior

Feature Gate Issue: #2562

[apfitzge]

these can be u16

[tao-stones]

It could, made them u32 mainly because they are used to calculate cu-limits, which is u32, saves a bunch of try_into(). Honestly I don't see it, but is changing them into u16 necessary?

[apfitzge]

we shouldn't allocate like this per transaction

[tao-stones]

This is sort of proof of concept - it implements the function, but not great for allocation.

To improve performance, maybe need @buffalojoec PR, then Vec<pubkey> can be replaced with maybe_builtin: [u12; 10] - a fixed array that maps BUILTINS, each u12 counts number of builtin instructions. That way sanitize can refer to BUILTINS for migration feature id.

[pgarg66]

This dependency is added specifically for a test. Can the test be reworked to move this dependency out of SVM related crates? We are trying to keep the deps to a minimum so that SVM can be moved to its own Github repo.

[tao-stones]

thanks for pointing this out, change in 34f497d