pgsql: Prevent walsummarizer from getting stuck at a timeline switch.

Prevent walsummarizer from getting stuck at a timeline switch.

As previously coded, walsummarizer only wants to read WAL from a file
where the TimeLineID in the filename exactly matches the TimeLineID being
summarized. But in some cases, when a timeline switch occurs, the WAL file
from the old timeline is not archived, because it's never completely
filled, so the only way to obtain the contents of that last partial
segment is to read from the first segment on the new timeline. Teach
WAL summarizer to do that, and add a test case to make sure that it
works.

Reported-by: Nick Ivanov <nick(dot)ivanov(at)enterprisedb(dot)com>
Reviewed-by: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Tested-by: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Reviewed-by: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>
Reviewed-by: Zhijie Hou <houzj(dot)fnst(at)fujitsu(dot)com>
Reviewed-by: Thom Brown <thom(at)linux(dot)com>
Discussion: http://postgr.es/m/CA+Tgmobr27GpKDZx3_ezW2+C5_g18i+jSK3sGF_cR-_ESv5N5A@mail.gmail.com
Backpatch-through: 17

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/499d9eabb5698ff6091b5a186acd7d05cf9d4c2b

Modified Files
--------------
src/backend/postmaster/walsummarizer.c | 173 +++++++++++++++++++++++++++---
src/bin/pg_walsummary/meson.build | 1 +
src/bin/pg_walsummary/t/003_tli_switch.pl | 149 +++++++++++++++++++++++++
3 files changed, 309 insertions(+), 14 deletions(-)