Generalize `ForeignAccountInputs` to work with the native account

[igamigo]

Not for this PR, but I wonder if we should just have one general AccountInputs. It could look something like:

pub struct AccountInputs {
    account_header: AccountHeader,
    storage_header: AccountStorageHeader,
    code_header: AccountCodeHeader,
    witness: AccountWitness,
    storage_map_proofs: Vec<SmtProof>,
    vault_proofs: Vec<SmtProof>,
}

pub struct AccountCodeHeader {
    procedures: Vec<AccountProcedureInfo>,
}

This struct would contain the data needed to load the account into the transaction kernel, irrespective of whether this is a foreign or native account.
Originally posted by @bobbinth in #1229 (comment)

[igamigo]

With the above, we'd also have to generalize the way the advice inputs are created (from the transaction args) at the moment of transaction execution.

One thing that might be worth noting is that the above struct (and the current ForeignAccountInputs) contains some redundancy because all of the account_header fields are contained in the other components, except for AccountHeader::nonce and AccountHeader::vault_root, so we could get rid of account_header in favor of the other two fields if we wanted to make it as succinct as possible.

[bobbinth]

One thing that might be worth noting is that the above struct (and the current ForeignAccountInputs) contains some ambiguity because all of the account_header fields are contained in the other components, except for AccountHeader::nonce and AccountHeader::vault_root, so we could get rid of account_header in favor of the other two fields if we wanted to make it as succicnt as possible.

Good point! We could do something like this:

pub struct AccountInputs {
    account: PartialAccount,
    witness: AccountWitness,
}

pub struct PartialAccount {
    account_id: AccountId,
    nonce: Felt,
    code_header: AccountCodeHeader,
    storage_header: AccountStorageHeader,
    vault_root: Digest,
    storage_map_proofs: Vec<SmtProof>,
    vault_proofs: Vec<SmtProof>,
}

pub struct AccountCodeHeader {
    procedures: Vec<AccountProcedureInfo>,
}

We could also replace vault_root and vault_proofs with something like PartialVault and do the same for storage (i.e., have PartialStorage instead of storage_header and storage_map_proofs).

[igamigo]

I've implemented this on #1311.
There is a small problem caused by stripping the full AccountCode from the account (in PartialAccount), however.
Specifically, the list of AccountCode (both for native and foreign accounts) needs to flow into the TransactionWitness after the execution is over which means they would now need to be tracked separately all the way until reaching the witness, making things more complex.

For now, I've left AccountCode within PartialAccount to make things simpler. I've also added AccountCodeHeader though it's left unused in my PR in case we want to change the way this works.