filter blog by topics on render article route

[marjisound]

What does this change?

This PR adds logic for filtering liveblog on render article route. It'd add implementation for pagination when top mention result is provided.

• only gets top mentions when key event filter is switched off
• Adds TopicsLiveBlog BlockRange for when first page is requested with topics
• Updates firstPage logic to have correct pagination when top mentions result is provided
• Updates findPageWithBlock to have correct pagination when top mentions result is provided
• Refactors firstPage implementation and extracts the details into separate private functions
• Updates applyFilters implementation for when top mentions is provided
• Adds detailed tests for firstPage & findPageWithBlock for when top mentions is provided
• Updates DCRFake in order to enable testing of the the data passed to DCR
• Adds test for renderArticle endpoint

Note
This PR does not cover the renderJson route and as a result doesn't add logic for updates. This would be done in upcoming PRs.

paired with @joecowton1

Does this change need to be reproduced in dotcom-rendering ?

• No
• Yes (please indicate your plans for DCR Implementation)

Screenshots

What is the value of this and can you measure success?

Checklist

Does this affect other platforms?

• AMP
• Apps
• Other (please specify)

Does this affect GLabs Paid Content Pages? Should it have support for Paid Content?

• No
• Yes (please give details)

Does this change break ad-free?

• No
• It did, but tests caught it and I fixed it
• It did, but there was no test coverage so I added that then fixed it

Does this change update the version of CAPI we're using?

• No, all the existing database files are just fine
• Yes, and I have re-run all the tests locally and checked in all the updated data/database/xyz files

Accessibility test checklist

• Tested with screen reader
• Navigable with keyboard
• Colour contrast passed

Tested

• Locally
• On CODE (optional)

[marjisound]

Hi all, I know there's been discussion about naming of different models or classes. There's an upcoming PR that we're currently working on which is supposed to factor all these name changes #25133

[marjisound]

This PR was fully tested in code so I'll merge it to unblock the rest of the work. But if you have any feedback after the merge, please add them here and I'll make sure to address them in the next PR :)