The CheckUser API needs to be updated to support reading results from the three CheckUser result tables (cu_changes, cu_log_event, and cu_private_event). To do this, a similar strategy to Special:CheckUser has been implemented, where there is a separate class for each request type. These will extend a common abstract class which will be named ApiQueryCheckUserAbstractResponse and takes inspiration from AbstractCheckUserPager.
Acceptance criteria
- Have the ApiQueryCheckUserAbstractResponse abstract class created