Derive Field value operator sets from Views filter-handler data (!7) · Merge requests · project / entity_segment

Derives FieldValue's operator sets from each field's Views filter handler (views_data) instead of the hand-maintained data-type map.

New OperatorCategoryResolver service: views_data filter id → handler class → operator category by ancestry (Date→temporal, NumericFilter→numeric, StringFilter→string, BooleanOperator→boolean, InOperator→membership, else unknown). Keyed on the leaf's own entity type, so a reference-hop leaf resolves on the hopped-to type.
Promotes core views to a hard dependency (the settled API trade-off); the three contrib integrations remain optional. README updated.
FieldValue::getCategory() delegates to the resolver; DATA_TYPE_CATEGORIES removed; adds a membership category (reusing existing entity-query operators — no Views operator strings adopted).
Kernel tests pin all four behaviours (handler-drives-operators, field-module override, unknown fallback, hop-on-hopped-to-type).

Rebased on 1.0.x after #3612426 merged. Local: phpcs ✓, phpstan ✓, all test suites green.

Derive Field value operator sets from Views filter-handler data