refactor(lee): resolve Deploy's raw_payload from the top-level Message, drop ChainedCall::raw_payload

Deploy only ever runs natively (never inside a real zkVM guest), so a
chained call into it never needed to carry the bytecode through an
intermediary guest's own execution in the first place: the dispatcher
already holds the top-level Message for the whole transaction and can
resolve its raw_payload directly, at any chain-call depth. Un-ignores
loader_deploys_program_via_chained_call, previously blocked by the
believed need for guests to forward large payloads through their own
instruction_data.

ChainedCall::raw_payload is now dead code with this change (no guest
ever populated it) and is removed, along with every "raw_payload: None"
guest-side literal that existed only to satisfy the field.

examples/program_deployment/methods/guest/src/bin/simple_tail_call.rs

@@ -54,7 +54,6 @@ fn main() {
         instruction_data: chained_call_instruction_data,
         pre_states,
         pda_seeds: vec![],
-        raw_payload: None,
     };
 
     // Write the outputs.

examples/program_deployment/methods/guest/src/bin/tail_call_with_pda.rs

@@ -66,7 +66,6 @@ fn main() {
         instruction_data: chained_call_instruction_data,
         pre_states: vec![pre_state_for_chained_call],
         pda_seeds: vec![PDA_SEED],
-        raw_payload: None,
     };
 
     // Write the outputs.