[CT-88] Ownership chain history responses have no pagination

[mftee]

Overview

The module/ownership_chain module backs the README's documented /verify/:hash/history route, but for a document with a long transfer history there's no evident pagination — the full chain is returned in one response, which doesn't scale for documents that change hands many times over years.

Tasks

• Add pagination (cursor or offset-based) to the ownership-chain/history response
• Add a test asserting a long chain is returned across multiple pages rather than one unbounded response

Acceptance Criteria

• A document with a long transfer history is served via bounded, paginated responses

Notes for Contributors

Comment below to be assigned.

[Kenisank]

Hi maintainer, I would like to solve this issue