Clean up left over Bytecode code + some related testing fixes

[andresilva91]

Motivation

• Some code was left over from when we removed the non-blobs bytecode code
• Some places in tests were not using the bytecode blobs properly

Proposal

Fix those and properly mimic what we're doing with user contract/service code with blobs.

Test Plan

CI

Release Plan

• Nothing to do / These changes follow the usual release cycle.

[andresilva91]

• Create ApplicationDescription blob type #2612
• Introduce blob_bytes function #2611
• Return multiple blobs not found at once #2610
• Check storage in get_blobs #2609
• Clean up left over Bytecode code + some related testing fixes #2607 👈
• Miscellaneous fixes in AMM README #2606
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @andresilva91 and the rest of your teammates on Graphite

[afck]

ChainRuntimeContexts can now remain in memory for a long time, and for any number of blocks. For the contracts and services it makes sense to keep them in memory, because an application that has been used on a chain (e.g. non-fungible) it's likely that it will be used again.
But for other—potentially large—blobs (e.g. NFT data!) it's often the case that they get only used once (maybe the NFT is traded on this chain and moves elsewhere). In that case, we shouldn't keep the blob in memory indefinitely.