🦺 Enhance CubeJS model with enums and improved type safety

[guimorg]

• Add Granularity and FilterOperators enums for better type checking and developer experience.
• Extend model classes with additional fields like compare_date_range, logical operators for filters, and offset parameter for pagination.
• Make values field optional in Filter class to support operators that don't require values.

[guimorg]

This PR aims to bring a bit more semantic and allow for some validations to take place on the model.

Most of the model is based on the documentation provided by CubeJS here:

https://cube.dev/docs/product/apis-integrations/rest-api/query-format

But also on some historical queries we've already performed, for example order is documented as an array of tuples, but it also accepts a plain dict/Object/map.

[guimorg]

I'm still unsure if leaving enums as the proposed by pylint is the best semantic or even visual queue. Maybe leaving it all as snake case, or camel cases. idk. I feel sometimes enums are just plainly yelling at me lol

[rafaelleinio]

lgtm! if you want to change the README.md example with the new enum definition, feel free to do that as well

[rafaelleinio]

I'm still unsure if leaving enums as the proposed by pylint is the best semantic or even visual queue. Maybe leaving it all as snake case, or camel cases. idk. I feel sometimes enums are just plainly yelling at me lol

Yeah, I feel the same, it's ugly IMO. But I think is a pattern already too common and followed by the python community.