[FEATURE] Decouple `BaseWallet` and `Account`

[shiqicao]

Problem Statement

We have a different account than Account, but unfortunately BaseWallet has a hard dependency on Account, which blocks us. BaseWallet can take a generic type parameter to specify a mini requirement of account, which generalize the BaseWallet implementation, for example,

interface Account {
    createTxExecutionRequest(..): ...;
    createAuthWit(...): ...;
}

class BaseWallet<A extends Account> {
    abstract getAccountFromAddress(addrss: AztecAddress): Promise<A>;
}

This change also makes user very clear what methods BaseWallet actually using.

Proposed Solution

see Problem statement

Example Use Case

No response

Alternative Solutions

No response

Additional Context

No response