v2.1: Accounting migrating builtin programs default Compute Unit Limit with feature status (backport of #3975)

[mergify]

Problem

When a builtin program migrated into sbpf, it should no longer be considered as 'builtin', therefore its default Compute Budget Limit should change from 3K to 200K CU, per #3799. It is currently not supported by Compute Budget Instruction processing.

Summary of Changes

• Add fixed-length (currently 3 entries) vector MigrationBuiltinFeatureCounter to transaction static meta;
• Counts migrating builtin features gates during try_from()
• Check feature_set to resolve if builtin has migrated during calculate_default_compute_unit_limit() if Compute Unit Limit was not requested.

Fixes #

---

This is an automatic backport of pull request #3975 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 9379fbc has failed:

On branch mergify/bp/v2.1/pr-3975
Your branch is up to date with 'origin/v2.1'.

You are currently cherry-picking commit 9379fbcba4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Cargo.lock
	modified:   builtins-default-costs/Cargo.toml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   builtins-default-costs/src/lib.rs
	deleted by us:   compute-budget-instruction/Cargo.toml
	deleted by us:   compute-budget-instruction/src/builtin_programs_filter.rs
	both modified:   runtime-transaction/src/compute_budget_instruction_details.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[tao-stones]

Did first round of conflicts fix. Need to rebase after #3931 is merged to 2.1

[t-nelson]

bit much for a backport innit?

[tao-stones]

bit much for a backport innit?

Ya it is. It is currently an accumulation of #3931 and the actual BP. Once #3931 is backported, I'll rebase this one then invite reviwers.

[tao-stones]

running on ds2 since slot 313127967, epoch 724

[t-nelson]

why? stop 😭

if you need to bp another pr, bp another pr. stop piling stuff into what's already unreviewable

[tao-stones]

why? stop 😭

if you need to bp another pr, bp another pr. stop piling stuff into what's already unreviewable

Ah, I'm sorry. You are right that #3768 should be bp-ed separately, if it's restrictively needed. I'll fix it.