Update filtering issues to cover storing filter/group information in the backend.

[kgodey]

Problem

We should store filter and group information in the backend so that the frontend doesn't need to know anything about types.

Proposed solution

The currently open filtering tickets should be updated to account for this.

Additional context

From @pavish on Matrix:

It would be nice if we can also store the allowed filter/grouping options on the backend.

This way, the frontend does not have to know about types, and it allows us to use any new types by just creating it on the backend during runtime, without needing to update any code.

It also involves storing additional meta data, like certain grouping/filtering options would require multiple values (eg., range), or no values at all (eg., is_null). So, we need to define a format, that also specifies this kind of information.

[kgodey]

This is done.