feat(pagination): make pagination class consistent and use the same parameters DEV-1393

[Guitlle]

🗒️ Checklist

1. run linter locally
2. update developer docs (API, README, inline, etc.), if any
3. for user-facing doc changes create a Zulip thread at #Support Docs Updates, if any
4. draft PR with a title <type>(<scope>)<!>: <title> DEV-1234
5. assign yourself, tag PR: at least Front end and/or Back end or workflow
6. fill in the template below and delete template comments
7. review thyself: read the diff and repro the preview as written
8. open PR & confirm that CI passes & request reviewers, if needed
9. delete this section before merging

📣 Summary

Replace custom pagination classes with a default pagination class with customizable parameters

💭 Notes

The DefaultPagination class replaces other custom classes and enables developers to set custom class attributes via a class method custom_class(cls, **kwargs) . It includes functionality for fast optimized queryset counts (by setting the attribute fast_count=True) and no counts at all (by setting the attribute no_count=True). Supports start as an alias for offset by default. Supports having a page query parameter that is translated into limit / offset parameters.

👀 Preview steps

1. Have an account and a project with many submissions
2. Go to the project data view and browse the submissions
3. Go to the audit logs and click on the next page button
4. Ensure there are no error messages related to pagination responses in the frontend or in the backend logs. All paginated views should work ok