AlgoScan

- Now, only signer can cancel shared account async transaction
- Fixed unreported issue with JointAccountPendingTransactionOverlay pop-up animation. Now capsules and buttons will animate properly when view appear on the screen.
- Added cancel transaction confirmation dialog, it will be shown when user tap on the "Cancel" button on the pending shared transaction overlay.
- hide backup account banner for joint accounts
- add joint account participants addresses to inbox fetch request
- joint account analytic events added
- Fixed reported Joint account's UI issues.
- add quick actions inbox badge if there are joint account requests
- Added missing feature. Now co-signers that aren't transaction's proposer will be able to sign transaction using ledger.
- add quick actions inbox badge if there are joint account requests
- inbox texts fixed
- filter out joint accounts from fund and dapps
- Removed doubled BLE discovery trigger
- Implemented "on success" behaviour for BLE/Ledger flow on SendTransactionPreviewScreen

Follow the same approach as getbit/setbit/getbyte/setbyte: accept any bytes arg for the first operand and use `_bytes_length_lower_bound` to get a tight bound for `BytesConstant` and the AVM maximum (MAX_BYTES_LENGTH) otherwise. Unifies substring3's previously separate constant-bytes and runtime-bytes arms into one. Doesn't touch the extract family since its immediate-form offsets are capped at 255 (can't exceed MAX_BYTES_LENGTH on its own).