Block Library: Add the Comments Pagination block

[DAreRodz]

Description

This block works as a container for other pagination blocks that render links to navigate through the list of comments. It basically works the same as the Query Pagination block, but for comments.

It has the same settings:

• changing layout and colors
• choosing different styles for next/prev arrows.

Will close #35007

How has this been tested?

1. Modify the Single Post template, adding a Comments Query Loop block
2. Add inside the Comments Pagination block
3. Check that the layout and color settings work (tested only in the editor)
4. Check that the arrow setting works as expected (tested only in the editor)

Types of changes

• New feature

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

[DAreRodz]

These blocks are meant to be changed once the rest of the comments-pagination blocks are created.

[DAreRodz]

Again, these blocks should be replaced with the comments-pagination ones.

[cbravobernal]

Nice job! It seems that we have to include the schema in order to pass the tests.
Also, do we have to create the fixtures? In order to do that, we have to create the core__comments-pagination-block.html with the content that is created on the code editor. Then paste it and then run npm fixtures:generate

[DAreRodz]

Thanks for the review @c4rl0sbr4v0 🙇 You're right, I forgot to add the fixture for the new block. Fixed now. 👍

[cbravobernal]

Next question I have is. Should we merge it before having the other ones (core/comment-pagination-*? How would we approach this?

Leaving as is right now, it does not crash, right?

[gziolo]

Next question I have is. Should we merge it before having the other ones (core/comment-pagination-*? How would we approach this?

Yes, we can also land this PR without inner blocks and address that in follow-up PRs. If we take that route we should rather hide this block from the inserter temporarily.

[aristath]

The PR needs to be rebased as there are now conflicts with trunk 👍

[cbravobernal]

Yes, we can also land this PR without inner blocks and address that in follow-up PRs. If we take that route we should rather hide this block from the inserter temporarily.
The PR needs to be rebased as there are now conflicts with trunk 👍

I updated the code with the requests and created a new PR, cherry-picking @DAreRodz commits. It is easier for me than making the updates on their repo. And also I included in this PR a Merge commit without wanting to.

#36872 closes this PR.