feat!: MultisigAccount and LogicSig with signer interfaces

[joe-p]

This PR started as just multisig, but now also includes logic signatures since they are partly intertwined. Both the lsig and msig abstractions present in algosdk and utils require direct usage of secret keys. The abstractions in this PR work entirely based on signing callbacks. This improves security (secret keys are no longer passed around) and makes multisigs and logicsigs compatible with external KMS.

The following function was also added to make it easy for anyone without Algorand knowledge to generate Algorand-specific signing functions with type safety, auth address handling, and proper domain separation:

const keypair = nacl.sign.keyPair()
const rawSigner = async (bytesToSign: Uint8Array): Promise<Uint8Array> => {
  return nacl.sign.detached(bytesToSign, keypair.secretKey)
}

const addressWithSigners = generateAddressWithSigners(keypair.publicKey, rawSigner)

expect(addressWithSigners.addr.publicKey).toEqual(keypair.publicKey)
expect(addressWithSigners.signer).toBeDefined()
expect(addressWithSigners.lsigSigner).toBeDefined()
expect(addressWithSigners.programDataSigner).toBeDefined()
expect(addressWithSigners.mxBytesSigner).toBeDefined()

It should be noted that this is a fairly significant breaking change for lsigs and msigs but the changes only affect those using in-memory secret keys with these abstractions whcih should hopefully be a small percentage of production code.

TODOs in this PR

• Test coverage
• Assess stateless functions for overlap and distill class functionalities as functions

Related TODOs in follow up PRs

• Refactor Account abstraction
• Separate algod25 package for working with 25-word mnemonics
• Refactor environment mnemonic logic within utils
• HD wallet package
• Determine how to handle test account generation

[joe-p]

Putting this in draft because I realized lsig and msig are a bit intertwined, so I wil update this PR with lsig changes as well