FIX: 1631

[MrTob]

Fix rows per page selection in account entries (#1631 )

The "rows per page" selector in account entries didn't work correctly because the form was submitting to the wrong endpoint. This was happening because it used custom_pagy_url_for which directed the request through the parent resource's show action instead of the entries endpoint.

Changes

• Modified the form in _pagination.html.erb to submit directly to account_entries_path with the correct account_id
• Added turbo_frame targeting to ensure proper frame updates
• Added explicit parameter preservation for tab and search context
• Removed custom_pagy_url_for usage from the form (kept for pagination links)

The form now correctly submits to the entries endpoint while preserving all necessary context parameters, allowing proper rows per page updates within the Turbo Frame.

[zachgoll]

@MrTob this is definitely the cause of the bug, but I think we should be careful adding to much responsibility to this _pagination.html.erb partial. This partial is meant to be agnostic of what view it is rendered in, so I don't think we should be adding checks such as defined?(@account) ? account_entries_path(...) : ...

For the moment, I think a clearer option would be to duplicate this partial into an entry-specific one, such as views/account/entries/_pagination.html.erb

That way, we can be highly specific with our intended routes and remove a lot of the conditional logic.

Yes, this will result in a bit of code duplication, but I think the clarity tradeoff is worth it at this stage.

[zachgoll]

@MrTob be sure to request a review when this is ready again and I can take a final look!