Spurious "Heartbeat response addressed to different node" log lines

[jcsp]

Log noise seen in this run with an unrelated failure: https://buildkite.com/redpanda/redpanda/builds/13482#01825f42-567a-45e6-a9da-1b6a1bb7061e

On an error response, the revision ID is unset:

WARN  2022-08-02 16:40:18,429 [shard 0] r/heartbeat - heartbeat_manager.cc:321 - Heartbeat response addressed to different node: {id: {3}, revision: {-9223372036854775808}}, current node: {id: {3}, revision: {32}}, response: {node_id: {id: {2}, revision: {-9223372036854775808}}, target_node_id{id: {3}, revision: {-9223372036854775808}}, group: {18}, term:{-1}, last_dirty_log_index:{-9223372036854775808}, last_flushed_log_index:{-9223372036854775808}, last_term_base_offset:{-9223372036854775808}, result: group_unavailable}

In some cases the node ID itself is unset:

RedpandaService-0-140064439343216/docker-rp-9/redpanda.log:WARN  2022-08-02 16:42:10,524 [shard 0] r/heartbeat - heartbeat_manager.cc:321 - Heartbeat response addressed to different node: {id: {-2147483648}, revision: {145}}, current node: {id: {2}, revision: {145}}, response: {node_id: {id: {-2147483648}, revision: {83}}, target_node_id{id: {-2147483648}, revision: {145}}, group: {5}, term:{4}, last_dirty_log_index:{8308}, last_flushed_log_index:{8308}, last_term_base_offset:{-9223372036854775808}, result: success}