Feature: Early verification of account modifications in BorrowedAccount

[Lichtso]

Problem

This is a continuation of #25380.

Currently, for BPF programs the verification cost is:

• One data copy from AccountSharedData to create or update the PreAccount
• One data copy from the BPF program into the AccountSharedData so we can compare it against PreAccount
• The actual comparison in PreAccount (this is skipped if the data is allowed to be modified)

Assuming that copies and comparison incur a similar cost (as they both need to access two different pointers, polluting the data cache), we could reduce this cost by 50% up to 66% for every account in every ABIv0 and ABIv1 BPF program executed. Built-in programs would also profit, reducing their verification cost by almost 100%. In ABIv2 BPF programs will be like built-in programs in this regard.

Summary of Changes

This PR introduces the feature enable_early_verification_of_account_modifications which controls the switch from the current behavior to the following:

1. Account modification errors are thrown earlier (hence the name of the feature). Specifically, they occur the moment they are attempted, not at the begin / end of instructions and CPI. The primary motivation is to get rid of PreAccount and all the redundant data copies and data comparisons that come with it. As a side effect, this should make debugging easier because we can get the call stack where the error occurs.

2. Similarly to the deprecation of PreAccount, AccountsDataMeter will also be deprecated and its functionality replicated inside TransactionContext. This was necessary as the AccountsDataMeter is currently updated and verified from withing the PreAccounts.

3. As a consequence, first corrupting (meta)data and then later correcting it into a valid state again won't fly anymore. Every change will have to be valid on its own. This however, does only apply to the runtime and built-in programs, not to BPF programs of ABIv0 and ABIv1 (all currently deployed programs) as they will continue to have their checks at the deserialization edge.

4. Failed attempted account modifications used to be counted as modifications, now they are not recorded as "touched" anymore. For BPF programs, all accounts which are modifiable however, will be counted as "touched" even if their data did not change.

5. All the explicit / dedicated account modification tests inside InvokeContext, PreAccount and AccountsDataMeter are disabled / become unreachable.

6. The loader and built-in tests on the other hand, become stricter as they now have to adhere to all account modification rules.

7. Two tests to trigger InstructionError::UnbalancedInstruction (which was not covered before) were added.

---

Feature Gate Issue: #26589

[jackcmay]

I'm not too worried about rent_epoch anymore since accounts must be rent-exempt. We will either have to continue setting it for ABIv1, or maybe feature gate a deprecation of it which sets it to some acceptable value that is least likely to break existing programs.

[codecov]

Codecov Report

Merging #25899 (3fbf0c7) into master (1165a7f) will increase coverage by 0.0%.
The diff coverage is 77.5%.

❗ Current head 3fbf0c7 differs from pull request most recent head 61a171d. Consider uploading reports for the commit 61a171d to get more accurate results

@@            Coverage Diff            @@
##           master   #25899     +/-   ##
=========================================
  Coverage    81.9%    81.9%             
=========================================
  Files         631      633      +2     
  Lines      174252   175374   +1122     
=========================================
+ Hits       142728   143798   +1070     
- Misses      31524    31576     +52     

[Lichtso]

I think I addressed all review comments, CI is passing, no merge conflicts ...
@jstarry @ryoqun @brooksprumo Can you once more approve so we can finally merge this?

[brooksprumo]

The accounts resize delta changes look good to me.

[ryoqun]

lgtm. master piece pr. :)