Unclear outcomes `assert_failed` and `panic` in proof runs

[jberthold]

Some of the proof branches end up in calls to assert_failed or panic. These need to be investigated individually to find out what logic leads to the invalid state.

[jberthold]

Notes: after some investigation:

• Related to some of the failures: unrecognised vacuous branches due to #mapOffset Chains of #mapOffset functions #81
• The sys::rent::Rent::get() cheat code should provide the same symbolic rent on each invocation, but currently creates a fresh value each time. Cheat code for sys::rent::Rent::get() must return the same Rent each time #96

[jberthold]

Some of the proofs fail because they use Rent::from_account_info_unchecked().
This function checks the PubKey given in the AccountInfo against the (hard-wired) PubKey for the Rent sysvar:
https://github.com/anza-xyz/pinocchio/blob/74a7b51af47acd791c239cd142c7317639de6978/sdk/pinocchio/src/sysvars/rent.rs#L92-L103
Tests fail on the branches where the PubKey in the input data is unequal to the Rent's key. The properties must be adjusted to reflect this.

Affected proofs include the initialize_mint family of proofs (suffix '' and 2, variants _freeze and _no_freeze)