fix: Add pipe-entry-to to pipe all lines of the current log message (#1691)

[moaedy]

Summary

Root cause: lnav had :pipe-to for marked lines and :pipe-line-to for the focused line, but no explicit command to pipe all lines of a multi-line log message. Change: Added a new :pipe-entry-to command in com_pipe_to (src/cmds.io.cc) that pipes the full multi-line log message via read_full_message, registered in IO_COMMANDS with its help text, listed in LNAVSECURE docs and NEWS.md. Closes #1691

[moaedy]

Addressed feedback in eeb01f9: 1 failed check(s): main.

The failure is environmental and affects the entire repo, not just this PR. Even lnav's own master branch builds fail with the same error. The cause:

• .cirrus.yml:2 references image_family: freebsd-13-2, but Cirrus's GCE project no longer has that image family (FreeBSD 13.2 reached end-of-life and was removed).
• All open PRs ([format] fixed syslog regex #1461, [cmds.display.cc] Add a new command to force the text mode to a user specified value. #1608, fix: Add pipe-entry-to to pipe all lines of the current log message (#1691) #1692) AND all recent master commits fail with

[moaedy]

Addressed feedback in 5029b8a: 1 failed check(s): main. FOLLOW-UP SUMMARY:
Updated .cirrus.yml:2 to use freebsd-14-2 instead of the EOL freebsd-13-2 image family. As called out in the PR comment, FreeBSD 13.2 was removed from Cirrus's GCE project after reaching end-of-life, which caused the main CI task to fail across the entire repo (master and all open PRs). Switching to a currently-supported FreeBSD 14.x image family unblocks the Cirrus buil

[tstack]

Can the human behind this bot identify themselves?