Wrong encoding of call data when runtime apis moved to separate file

[Roznovjak]

After moving runtime apis to a separate file, we couldn't submit any TX from the polkadot js app. The issue was also with queryInfo as described here #10994. When compared encoded call data produced by the app and the runtime, call data from the app contained one additional zero byte.

• encoded signed TX from the polkadot js app: 0xfd0184 00 d435...
• the same TX encoded using the runtime: 0xf50184 d435...
  That zero byte is placed after the EXTRINSIC_FORMAT_VERSION and before the account data.
  It looks like the call data produced by the app can't be decoded and all TXs fail with the following error:

1002: Verification Error: Runtime error: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed WASM backtrace: error while executing at wasm backtrace: 0: 0x72cb39 - <unknown>!rust_begin_unwind 1: 0xc741 - <unknown>!core::panicking::panic_fmt::hfc6cd7a9f4893967 2: 0x5aa0f9 - <unknown>!TaggedTransactionQueue_validate_transaction: RuntimeApi, Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\nerror while executing at wasm backtrace:\n 0: 0x72cb39 - <unknown>!rust_begin_unwind\n 1: 0xc741 - <unknown>!core::pa…

• GH repository with the runtime producing the error, WITH runtime apis moved to a separate file.
• GH repository with the runtime NOT producing the error, WITHOUT runtime apis moved to a separate file.
  For testing, we were using zombienet.

Metadata produced by both runtimes are identical.