SIMD-0160: static instruction limit

[tao-stones]

Problem

Issue #8181 for SIMD-0160

Summary of Changes

• Add feature gate to start apply limit to transaction's top level instructions during sanitization.

Fixes #8181

[codecov-commenter]

Codecov Report

❌ Patch coverage is 98.91304% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.0%. Comparing base (84c5f28) to head (b13051f).
⚠️ Report is 2096 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #8182    +/-   ##
========================================
  Coverage    83.0%    83.0%            
========================================
  Files         827      827            
  Lines      362713   362853   +140     
========================================
+ Hits       301254   301389   +135     
- Misses      61459    61464     +5     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[apfitzge]

64ix 🫡

[mergify]

If this PR represents a change to the public RPC API:

1. Make sure it includes a complementary update to rpc-client/ (example)
2. Open a follow-up PR to update the JavaScript client @solana/kit (example)

Thank you for keeping the RPC clients in sync with the server API @tao-stones.

[apfitzge]

On it's own this PR does not support the transition into the feature correctly, but since #8183 has already been merged it seems this will work as intended.

My thought here was that RuntimeTransaction/SanitizedTransactionView types are not sufficient because we create these values ahead of time and store until we become leader. If ingested before the activation these can get past the filters of this PR for block-production, and a leader could include them. However, since #8183 we do not even reach this stage and they are dropped before we get here.