Rewriting remote links to local not working

### Requirements - [x] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support or the [matrix chat](https://matrix.to/#/#lemmy:matrix.org). - [x] Did you check to see if this issue already exists? - [x] Is this only a feature request? Do not put multiple feature requests in one issue. - [x] Is this a backend issue? Use the [lemmy-ui](https://github.com/LemmyNet/lemmy-ui) repo for UI / frontend issues. - [x] Do you agree to follow the rules in our [Code of Conduct](https://join-lemmy.org/docs/code_of_conduct.html)? ### Is your proposal related to a problem? The Voyager for Lemmy app uses the v3 `federated_instances.linked` endpoint in order to determine if a domain is a Lemmy instance (or Piefed instance). The reason pagination is a real problem for Voyager is that the entire linked-instances list is synchronized to the local client once every 12 hours and consulted during click interception (synchronously) to decide whether to call `e.preventDefault()` and resolve in-app, or let the browser/native handler take the link. I understand that the instances array is paginated in v4 because it's such a large array. However, it's easy to aggressively cache this list in Lemmy, right? And also Voyager aggressively caches this list to only fetch once per day, per client. ### Describe the solution you'd like. Unpaginated `federated_instances.linked` list in an aggressively cached API endpoint (no query params) ### Describe alternatives you've considered. I'm not sure if there is a good alternative. Maybe I could have a centralized API for this list, but that is not ideal. ### Additional context _No response_