Fix swapped labels in the command type mismatch message

[thinkinginmath]

Fixes #96.

CommandTypeMismatchError printed the handler's command as what the previous execution recorded, and the recorded command as what the current execution attempts.

Every caller constructs the error with the recorded command as actual and the handler's command as expected:

• RawMessage::decode_to, which PopJournalEntry uses during replay;
• the lazy and eager state replay paths.

This PR swaps the two arguments in Display and documents the fields. No caller changes.

Test

journal_mismatch::command_type_mismatch_names_recorded_and_attempted_commands replays a recorded Run at index 1 while the handler writes output, then checks both labels in the emitted ErrorMessage.

• Before the change: it fails with the swapped message: recorded the following: 'handler return' (index '1') / attempts to perform the following: 'run'.
• After the change: it passes.

Checks run locally

• cargo fmt --all -- --check
• cargo clippy --all-targets --workspace -- -D warnings, with default features and with --all-features
• cargo test: 256 library tests pass with default features, 259 with --all-features.

tests/bootstrap.rs fails locally only because protoc isn't installed; it fails the same way on main, and this change doesn't touch the protocol.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[thinkinginmath]

I have read the CLA Document and I hereby sign the CLA

[slinkydeveloper]

Thanks