[abstraction] Add support for AccountAbstraction

[GhostWalker562]

Description

This pull request introduces several new features and improvements related to account abstraction. The changes include adding new examples, new tests, and updating core account classes to support account abstraction.

• Added support for AbstractedAccount which enables signing AA transactions using a custom signer
• Added support for account.abstraction namespace which supports basic authentication function apis including adding functions, removing functions, and checking for whether functions exist.
• Added E2E test suite
• Added E2E examples

Test Plan

• tests/e2e/abstraction.test.ts
• enable and disable account abstraction
• enable account abstraction, send a transaction, and disable all account abstraction
• enable custom account abstraction, send a transaction with custom signer, and send a transaction with an invalid signer

Related Links

• [AIP-104][Discussion] Account Abstraction aptos-foundation/AIPs#513

Checklist

• Have you ran pnpm fmt?
• Have you updated the CHANGELOG.md?

[lightmark]

lgtm in general.
Just 2 cents:

1. serialize fixed bytes for authenticator?
2. verify sdk for permissioned delegation works.

[networkdm]

Hi @GhostWalker562, I'm getting the error Failed to deserialize input into SignedTransaction: unexpected end of input when running examples and tests. This is happening with version 1.26, deployed on both Devnet and Testnet. Or should I run a local node?

My Aptos CLI version is 6.0.2.

  ● abstraction api › enable account abstraction, send a transaction, and disable all account abstraction › should be able to send a transaction using acount abstraction

    AptosApiError: Request to [Fullnode]: POST https://api.devnet.aptoslabs.com/v1/transactions (trace_id:53a3e82172ae45fac8b89f21eaba68c6) failed with: {"message":"Failed to deserialize input into SignedTransaction: unexpected end of input","error_code":"invalid_input","vm_error_code":null}

      117 |   // We have to explicitly check for all request types, because if the error is a non-indexer error, but
      118 |   // comes from an indexer request (e.g. 404), we'll need to mention it appropriately
    > 119 |   throw new AptosApiError({ apiType, aptosRequest: aptosRequestOpts, aptosResponse });
          |         ^
      120 | }
      121 |

      at aptosRequest (src/client/core.ts:119:9)
      at submitTransaction (src/internal/transactionSubmission.ts:327:22)
      at Object.<anonymous> (tests/e2e/api/abstraction.test.ts:89:19)

[GhostWalker562]

@networkdm Sorry pushed a small issue with network deserialization late last week. Reverted that change and everything should work normally now

[lightmark]

the example is confusing.

[networkdm]

@GhostWalker562 Suddenly aptos.fundAccount is not working. I still can fund account using aptos account fund-with-faucet command on Devnet and test cases pass with manually funded accounts though.

[GhostWalker562]

@networkdm The devnet indexer is currently down which fundAccount relies on for awaiting transaction confirmations. I believe it's being worked on to bring it back up