Add support for remaining accounts resolution

[lorisleiva]

Adds two strategy for resolving remaining accounts on a given instruction:

• arg, which expects an array of PublicKey, Signer or both as an (extra) argument, and use that arg to fill remaining accounts.
• resolver for custom remaining accounts resolution.

For example, imagine the following example that burns Compressed NFTs and accepts the "Proof" of the leaf to burn as remaining accounts.

await burn(umi, {
  // ...
}).sendAndConfirm(umi);

Given an array of PublicKey as the Proof, before this PR we would need to do the following:

const proofs = [...];

await burn(umi, {
  // ...
})
  .addRemainingAccounts(proofs.map(pubkey) => {
    pubkey,
    isSigner: false,
    isWritable: false,
  })
  .sendAndConfirm(umi);

After this PR, we can now pass the proof directly as an extra argument of the burn instruction like so:

const proofs = [...];

await burn(umi, {
  proofs,
  // ...
}).sendAndConfirm(umi);

To make this work, we simply need to tell Kinobi that the remaining accounts of the burn instruction rely on an extra argument called proof.

kinobi.update(
  new k.UpdateInstructionsVisitor({
    burn: {
      args: {
        // Add the "proof" extra argument defaulting to an empty array.
        proof: {
          type: k.arrayTypeNode(k.publicKeyTypeNode(), { size: k.remainderSize() }),
          defaultsTo: k.valueDefault(k.vList([])),
        },
      },
      // Use the "proof" argument to fill remaining accounts.
      remainingAccounts: k.remainingAccountsFromArg('proof'),
    },
  })
);

[changeset-bot]

🦋 Changeset detected

Latest commit: b792c5b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@metaplex-foundation/kinobi	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[febo]

LGTM