feat: implement optionsEndpoint for dynamic field options

[stmh]

Summary

Implements GitHub issue #5: REST endpoint for dynamic enum options.

This feature allows select fields in config forms to fetch their options from a REST API at runtime, without requiring a full dynamic schema replacement.

Changes

• New OptionsEndpoint interface for configuring how to fetch options from REST endpoints
• New optionsService.ts with fetching, caching (TTL-based), and response normalization
• New templateResolver.ts - extracted shared URL template resolution from dynamicSchemaService
• ConfigForm integration - pre-fetches options via $effect and merges into enrichedSchema
• OpenAPI spec updated with OptionsEndpoint schema
• Comprehensive tests - 27 unit tests + 7 integration tests

Example Usage

const schema: ConfigSchema = {
  type: "object",
  properties: {
    api_key: {
      type: "string",
      title: "API Key",
      optionsEndpoint: {
        url: "/api/flowdrop/secrets",
        valuePath: "name",
        labelPath: "label",
        cacheTtl: 300000
      }
    }
  }
};

Verification

• Type check: 0 errors (npm run check)
• Tests: 228 tests pass (npm test)
• OpenAPI spec bundled successfully

Closes #5

[stmh]

hi @d34dman

here's a vibecoded submission for having dynamic options for select fields. So we do not need to use dynamicOptions just for a dynamic select.

Will try to test it tomorrow against a backend, but would be good to know if you are open for the contribution.

Not sure, why the ci is failing...

[d34dman]

fixed in 0.0.44