Frontend: Column filtering should adapt to datatype and endpoint capabilities in generic ResourceTable component

[MrSnyder]

Environment

• Python version: 3.8.10
• MrMap version: b23b7e2

User Story

As a developer, I want that the generic ResourceTablecomponent adapts to the backend datatypes and filtering capabilities so that the table filtering works in a reasonable and usable way right out-of-the-box.

Acceptance criteria

• Given I am a developer and I am applying the ResourceTable to a backend resource, when I have a non-filterable column, I want that the table does not offer filtering for that column.
• Given I am a developer and I am applying the ResourceTable to a backend resource, when I have a filterable date column, I want that the table offers date-picker based filtering for that column.

[jokiefer]

done