Snip 9 - Outside Execution

[PhilippeR26]

Motivation and Resolution

Solves issue #948 and replace stuck PR #1111 .
Implantation of the concept of execution of a transaction signed by an other account, standardized in SNIP-9.

Usage related changes

Most usages are explained in a dedicated guide, and detailed usage is explained in JSDoc.
2 main functions :
Creation of an outside transaction object with Account.getOutsideTransaction()

const call1: Call = {
  contractAddress: erc20Address,
  entrypoint: 'transfer',
  calldata: {
    recipient: recipientAddress,
    amount: cairo.uint256(3n * 10n ** 16n),
  },
};

const callOptions: OutsideExecutionOptions = {
  caller: executorAccount.address,
  execute_after: Math.floor(Date.now() / 1000) - 3600, // 1 hour ago
  execute_before: Math.floor(Date.now() / 1000) + 3600, // 1 hour from now
};

const outsideTransaction1: OutsideTransaction = await signerAccount.getOutsideTransaction(
  callOptions,
  call1
);

call1 can be an array of Call.

Execution from an other account with Account.executeFromOutside()

const response = await executorAccount.executeFromOutside(outsideTransaction1);
await provider.waitForTransaction(response.transaction_hash);

outsideTransaction1 can be an array of OutsideTransaction

Development related changes

• The Account interface has not been modified, to not impact the users of this interface(ArgentX, Braavos, ...).
• Due to excessive duration, tests are only using a SNIP-9 V2 account. Nevertheless separated tests have been performed with all cases (V1, V2, ERC165 compatible but SNIP-9 unsupported, no ERC165 support), and with mix of possibilities (multi OutsideTransaction including multicall, with several signer accounts (using several SNIP-9 versions).

NOTE
I don't know what is the current policy about enums, but an enum has been created in :
https://github.com/PhilippeR26/starknet.js/blob/b85379d05f8eb44a6cc49b583e1b6e406428ba0f/src/types/outsideExecution.ts#L77C1-L81C2

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing

[ivpavici]

mostly some grammar stuff and couple of questions from my side!

[penovicp]

lgtm

Note: I did a restructuring and rebase to PR #1111 so Konstantin can also be tracked by GitHub as a contributor.

[penovicp]

Don't change anything now but just wanted to mention that in the future when dealing with large objects as the expected result of tests using snapshots might be simpler.