feat: add code_address field in Message struct

[enitrat]

#[derive(Copy, Drop, Default, PartialEq, Debug)]
struct Message {
    caller: Address,
    target: Address,
    gas_limit: u128,
    data: Span<u8>,
    code: Span<u8>,
    value: u256,
    should_transfer_value: bool,
    depth: usize,
    read_only: bool,
    accessed_addresses: SpanSet<EthAddress>,
    accessed_storage_keys: SpanSet<(EthAddress, u256)>,
}

The information present in this struct is not enough to know who's code is being executed.

• If we optimize jumpdests with feat: implement Jumpdest caching in account storage #839, we would need to use code_address as the account to fetch jumpdests from
• For Regular Precompiles, we determine whether the target of a message is a precompile or not based on the code_address called, not the target. e.g.: delegatecall into a precompile
• For Kakarot Precompiles (calling Cairo contract), the whitelise on who can call a precompile is based on the address of the code that calls this precompile. https://github.com/kkrt-labs/kakarot/blob/f1e7ebb9599a563aec9ffabbf11739373de8587c/src/kakarot/interpreter.cairo#L71-L77 https://github.com/kkrt-labs/kakarot/blob/f1e7ebb9599a563aec9ffabbf11739373de8587c/src/kakarot/precompiles/precompiles.cairo#L138
• Upon deployment, the code_address in a message is 0
• in call opcodes the code_address is passed to generic_call and must be used to form the Message of the inner call frame.