AlgoScan

Leave sumhash experimental

# Conflicts:
#	src/avm/avm-ops-state-access.md
#	src/ledger/ledger-applications.md

Ledger: consolidate minimum balance requirement discussion

Co-authored-by: Cosimo Bassi <65770425+cusma@users.noreply.github.com>

Review by @cusma: make explicit that an application's creator is its
initial size sponsor, that the flat per-application contribution stays
with the creator, and that sponsoring a size is a route to an MBR
contribution distinct from creating the application.

The minimum balance requirement (MBR) was discussed in six places, with
the contributions of assets, apps, and boxes restated in more than one
file, and with separate statements about when a transaction fails for
not meeting the requirement.

Define the MBR of an account once, in Account State, as the base
requirement plus a contribution per resource, with each term pointing at
the section that specifies it. Keep the per-resource increments in the
sections describing those resources, and remove their duplicates.

State the failure condition once, in the account state validity
conditions, which already applied to all transaction types. The
condition there covered only assets; it now uses the account's full MBR,
and a second condition covers MaximumMinimumBalance, which was defined
as a parameter but never used.

Remove the claim that a box opcode fails when the application account
cannot cover the new requirement. The requirement is enforced once the
top-level transaction completes, so only the MBR change is immediate.

release: consensus upgrade aug 26