`ra:server_id()`s are currently formatted with `~w` which escapes atom
characters above the ASCII range. We can add the Unicode translation
modifier `t` to print the Unicode characters. For example, before:

    2026-03-21 12:19:33.235018-04:00 [info] <0.1008.0> queue 'qq-🐇' in vhost '/': granting vote for {'%2F_qq-\x{1F407}','rabbit-1@mango2'} with last {index, term} {0,0} for term 1 previous term was 0

After:

    2026-03-21 12:27:43.829863-04:00 [info] <0.1008.0> queue 'qq-🐇' in vhost '/': granting vote for {'%2F_qq-🐇','rabbit-1@mango2'} with last {index, term} {0,0} for term 1 previous term was 0

…ation-modifier

Use the Unicode translation modifier to log server IDs and cluster names

When a follower receives a pre-snapshot chunk, it uses `ra_log:write_sparse/3`
to write the entries to the WAL. However, `write_sparse/3` was passing the
entire `log_entry()` tuple `{Idx, Term, Cmd}` as the payload to the WAL,
instead of just the `Cmd`.

When the node is restarted, the WAL recovery process reads the payload and
wraps it in a new `{Idx, Term, Payload}` tuple. Because the payload was
already a full `log_entry()` tuple, the recovered entry became doubly-wrapped:
`{Idx, Term, {Idx, Term, Cmd}}`.

This caused a `badmatch` error in `rabbit_jms_machine:exec_read/3` when
`rabbit_jms_queue_client` attempted to read messages for delivery. The
`ra_server:transform_for_partial_read/3` function failed to strip the Raft
metadata because the doubly-wrapped entry did not match the expected
`{'$usr', ...}` pattern, causing raw Raft metadata to be returned instead
of the expected JMS message.

This commit fixes the issue by passing only the `Cmd` to the WAL in
`write_sparse/3`, matching the behavior of normal appends. A test case
has been added to verify that sparse writes survive recovery without
being doubly-wrapped.

When a new checkpoint write is in progress and release_cursor fires promote_checkpoint, the pending field gets overwritten, and the subsequent checkpoint completion clobbers the snapshot's pending state.

This type can be specified in a `ra_server:config()` so it's useful to
have it exported.

Export `ra:membership()` type

Do not clear pending if points to the checkpoint

Fix doubly-wrapped log entries after sparse write and recovery