Transaction events: Rust batch and block kernel integration

Part of #3803. Depends on transaction event integration.

Preserve and validate event payloads throughout the Rust batch and block kernels.

Scope:
- Include full event records alongside transaction headers in the Rust data types, construction logic, serialization, and proving interfaces used by the batch and block kernels.
- Validate that each transaction's event records match its event commitment. Reject missing or unexpected event collections and duplicate associations with a transaction.
- Preserve transaction associations and emission order so that block bodies contain the event data required for historical retrieval.
- Define and enforce aggregate event data limits in Rust.
- Verify that the updated transaction IDs bind events through the existing batch and block transaction commitments, without a separate event root.

Tests should cover serialization and deserialization, payload preservation, invalid transaction associations, commitment mismatches, and aggregate size limits.

This issue covers Rust only. Batch and block kernel MASM, recursive verification changes, node storage and query APIs, and SDK integration are outside its scope.