NOISSUE - Update timescale reader

[Musilah]

What type of PR is this?

This a feature because it updates the Timescale reader.

What does this do?

This PR updates the Timescale Reader to be able to use aggregation queries for timeseries data to be used in dashboards charts.

Which issue(s) does this PR fix/relate to?

NOISSUE on Magistrala

Have you included tests for your changes?

No

Did you document any new/modified feature?

No

Notes

[ianmuchyri]

{
    "offset": 0,
    "limit": 10,
    "format": "messages",
    "aggregation": "SUM",
    "interval": "1 minute",
    "total": 100,
    "messages": [
        {
            "time": 1708687680,
            "value": 18474
        },
        {
            "time": 1708687620,
            "value": 27894
        },
        {
            "time": 1708687560,
            "value": 3737
        }
    ]
}

The total count is not correct

[ianmuchyri]

Also for me to query for messages with the current implementation, I have to include aggregation and interval or it will not work. However, they are supposed to be conditional filters and the querying should work even without having to add them as filter parameters. Check on how to solve this.

[felixgateru]

The epoch time attached to an aggregation query such as MAX and MIN for a value is not the time in which the MAX or MIN value occured.

Which is different from when the value occured:

It makes sense for aggregation to do this but there is a concern that the reason you are doing aggregation is to not only get the value but also the exact time within your desired interval in which the max occured.

[rodneyosodo]

Also update api documentation to include the 2 filters