Remaining Test cases for QANet

[aneesharaines]

• Payments + snapp transactions from the same account are accepted
• A Snapp that's guaranteed to fail
• Txns with multiple proofs
• Update all the fields in one txn
• transactions are ordered fee per weight unit
• Max transactions per block

[psteckler]

Note: currently, we can't use the parties in a snapp as sender or receiver in a payment, so the test uses separate accounts for the payment. That will change eventually, and the test can be updated to use the parties accounts in the payment.

Matthew says: For that check, it appears that we need to update the old txn logic to check the permissions for sending/receiving and delegating, then it can be removed. (The old txns must not be able to exfiltrate funds from an account where send: Proof in the permissions.)

[deepthiskumar]

Suggest adding a test that check snark work is happening for snapp transactions. This might be higher priority than
the tests for Transactions are ordered fee per weight unit and Max transactions per block

Steps in the test:

1. Send a valid snapp transaction
2. send payments.
3. Wait for snarked ledger hash in the protocol state to change. (probably worth waiting for two ledger hash change to ensure snapps are in it)

Also, create a different profile for this test that uses a smaller scan state src/config/scan_state/small.mlh than what's in integration_tests.mlh. With this config and15-20 transactions, the snarked ledger hash should change at least twice

[psteckler]

All the checklist items are done.