allow stats in query config, probably set a flag so other methods know stats is in use
if stats is in query we might not need to force "@timestamp" to be there too because the aggregate might be messed up. So we'll need to deactivate incremental syncs for this case.
Figure out how to handle schema generation. We hard code the log ID as the PK but could make that configurable
I dont think we can paginate in batches so if we detect that the 10k batch limit is reached after aggregating then we need to throw and error
Currently if stats is used in the query then we throw an exception https://github.com/MeltanoLabs/tap-cloudwatch/blob/c83a222be106ac251af39fc2212b78a8b368af70/tap_cloudwatch/cloudwatch_api.py#L94. Ideally we'd allow stats by disabling some of the other features that dont work with it.
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_QuerySyntax.html