FE: UX: Column Filtering Support for Kafka connects table

[Vixtir]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Resolves #244

What’s Added

• Extended column meta definition for TanStack Table with a new property:
  meta.filterVariant?: 'multi-select'

• Added support for column-level filtering based on filter variant.

How to Enable Filtering for a Column

A column that supports filtering must define:

• accessorKey
• meta.filterVariant e.g. 'multi-select'
• filterFn (e.g. 'arrIncludesSome')

Example

const kafkaConnectColumns: ColumnDef<FullConnectorInfo>[] = [
  {
    header: 'Connect',
    accessorKey: 'connect',
    cell: BreakableTextCell,
    meta: { filterVariant: 'multi-select' },
    filterFn: 'arrIncludesSome',
  }, ...
]

URL Filter Persistence

Introduced queryPersister to sync filters with the URL.
This avoids polluting the main Table component with filter state management logic.

Columns filtering Persistence logic is extracted intoFilter/lib/persistermodule.

All persisters implement the following interface:

export interface Persister {
  getPrevState: () => ColumnFiltersState;
  update: (nextState: ColumnFiltersState, resetPagination?: boolean) => void;
}

The approach is scalable — new filter variants or persisters (e.g., localStorage, session, or in-memory) can be added with minimal changes.

Pagination can optionally be reset on filter change via the resetPagination argument.

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[fallen-up]

there’s a layout issue with the connector name column width.
if a connector has a long topic name, the connector name column becomes too narrow, while the topics column gets overly wide:

[fallen-up]

both fields now seem to have "protected" widths based on the maximum length of their content, but the result looks a bit odd - also not the good solution

• the objects no longer fit within the available width.
  

maybe it's worth considering setting a maximum length for each field, along with line wrapping, for example.

[Vixtir]

We try to discuss it with design, there are no solution fow overflow for topic tags yet

[yeikel]

Thanks for the new feature. Note that I filled an issue about this via #1177