Add base class for api/v1/trends/* controllers

[mjankowski]

Similar to #27797 for api/v1/instances and #27794 for api/v1/statuses this pulls out some common setup within the api/v1/trends/* controllers.

Most of the shared behaviour here is around pagination of the api response. I think there might be opportunity here for further extraction of a shared controller concern for pagination across all the API controllers, but starting small here with a few base class extractions.

With #27837 merged, we are at 100% coverage for these. With changes, coverage stays at 100% across controllers, behavior should not change.

[codecov]

Codecov Report

Attention: Patch coverage is 91.48936% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 85.01%. Comparing base (86500e3) to head (fcd6740).
Report is 241 commits behind head on main.

❗ Current head fcd6740 differs from pull request most recent head a8fe66d. Consider uploading reports for the commit a8fe66d to get more accurate results

Files	Patch %	Lines
app/controllers/api/v1/trends/base_controller.rb	95.65%	1 Missing ⚠️
app/controllers/api/v1/trends/links_controller.rb	87.50%	0 Missing and 1 partial ⚠️
...p/controllers/api/v1/trends/statuses_controller.rb	87.50%	0 Missing and 1 partial ⚠️
app/controllers/api/v1/trends/tags_controller.rb	87.50%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #27841      +/-   ##
==========================================
- Coverage   85.01%   85.01%   -0.01%     
==========================================
  Files        1059     1061       +2     
  Lines       28277    28308      +31     
  Branches     4538     4537       -1     
==========================================
+ Hits        24040    24065      +25     
- Misses       3074     3078       +4     
- Partials     1163     1165       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mjankowski]

Much of the base class extraction here accomplishes some of what the 3 other recent api/pagination-related PRs do. Will rebase this after those are in and see what's left.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has resolved merge conflicts and is ready for review.

[mjankowski]

Closing this in favor of the few remaining api pagination PRs that are open (which do almost all of this themselves).