feat: add fme_change_request resource

[MatiasCasaliSplit]

WHAT

Adds the read-only fme_change_request resource (list only), backed by GET /fme/api/v4/change-requests. It is Harness-native only. Scope is project by default (org_id + project_id). Pass resource_scope='account' to list across the whole account.

WHY

Agents can list pending change requests (FME approval workflow items) for feature flags and segments without knowing the flag or segment name first. For example, they can answer "what's waiting on my approval?" with filter=APPROVALS.

Changes

• src/registry/toolsets/feature-flags.ts: adds the fme_change_request resource (supportedScopes: ["account", "project"], FME_HARNESS_NATIVE_SCOPE_PARAMS).
  • Filters:
    • status (repeatable, defaults server-side to [REQUESTED])
    • filter (ALL default / APPROVALS / SUBMISSIONS)
    • environment_id (repeatable)
    • resource_type (FEATURE_FLAG / SEGMENT)
    • segment_type (STANDARD / LARGE / RULE_BASED)
    • offset / limit (harness_list size maps to limit, as on the other FME v4 lists)
  • Arrays and comma-separated strings for status / environment_id are sent as repeated query params. Enum values are canonicalized case-insensitively.
  • Invalid enums are rejected before any HTTP call. So are segment_type without resource_type=SEGMENT (and the reverse), and a missing org_id / project_id without resource_scope='account'.
  • skipCompact: the generic whitelist would drop resourceName, resourceType, environment, createdBy and approvalConfig.
• tests/registry/feature-flags.test.ts: 12 tests covering routing, account scope, filter mapping, CSV splitting and case canonicalization, validation errors, the extractor, and resource metadata.
• README.md: resource table row, a notes bullet, the toolset list, and the regenerated counts (260 resource types).

Testing

• pnpm build, pnpm typecheck, pnpm standards:check (79 passed), pnpm docs:check all pass.
• pnpm test: 171 files, 3937 tests, all passing.
• I ran the resource through the built registry and HarnessClient.buildUrl against a local service-web-admin, and every request returned 200 with the expected filtering. The calls covered:
  • project scope and account scope
  • multiple status values with filter=SUBMISSIONS and limit=5
  • filter=APPROVALS
  • resource_type=FEATURE_FLAG
  • resource_type=SEGMENT&segment_type=STANDARD
  • one and two environment_id values