Use page marker functionality for Republic

[svandaalen]

@BasLee has built support in TAV for rendering page breaks in the text component for Suriano. Can this functionality also be (easily) used for Republic? This might resolve some issues for resolutions that extend scan/page boundaries. Adding a marker where the page break happens gives the user a clearer picture of where a page/scan begins and ends.

For Republic, we can use the Page annotation. The Republic books have been digitised per opening, meaning you always see a verso and recto page. This means that we can't render a page break inside the scan. Take this resolution: https://textannoviz.republic-caf.diginfra.org/detail/urn:republic:session-4697-num-19-resolution-2. This resolution begins on f. 28v and ends at the top of f. 29r. Because the corresponding Page annotation pertains to both f. 28v and f. 29r, we can't mark the break between f. 28v and f. 29r. At least not with the current data we have. As I look in more detail at this, it appears that f. 28v and f. 29r have their own separate Page annotations: respectively https://annorepo.republic-caf.diginfra.org/w3c/republic-2024.07.18/7b13a661-796e-469f-acaa-a0e2ee0482a1 and https://annorepo.republic-caf.diginfra.org/w3c/republic-2024.07.18/38c73139-f5ba-4f3e-a233-6b50ce25f7ad. The first has a LogicalText range of 1578–1608 and the second of 1609–1657. So the above might be possible in the end.

Another challenge is which page/folio/scan number to render. Take the same resolution as above: the resolution is written on f. 28v and f. 29r, but the corresponding Page annotation has a body.metadata.opening of "157". This "157" refers to the page/opening in the physical book, but the book's producers used an alternative folio/page numbering. The first 93 pages of the book contain the index and are numbered per page (1 to 93). Then follows a blank opening, after which the resolutions start. At the place in the book where the resolutions start, they reset the numbering and instead of numbering per page, they number per folio. The user likely wants the actual, physical folio number rendered in the text rather than the page/opening number in the physical book.

The last challenge is that some resolutions have too many overlapping pages. Take the same resolution as above again: even though this resolution is written on one page/scan, AR returns four Page annotations (two more than needed?). Is this a problem for TAV? How does TAV know which Page annotation to use? Based on the start and end of Page annotations in relation to the Resolution annotation?