feat: add apiops configure command for guided filter & override config generation

[Copilot]

After apiops extract, there was no guided path for producing configuration.extractor.yaml or per-environment override files — users had to author them from scratch with deep schema knowledge.

New command: apiops configure

Scans extracted artifacts, then either interactively guides the user or applies best-effort defaults to produce:

• configuration.extractor.yaml — API filter (selected or all)
• configuration.<env>.yaml — per-environment overrides (one per --environments value)

# Interactive (default when TTY detected)
apiops configure

# Non-interactive, custom environments
apiops configure --non-interactive --environments dev,staging,prod

New / changed files

Core implementation

• src/services/artifact-scanner.ts — scans artifact dir for APIs (strips ;rev=N duplicates), secret named values, backend URLs, loggers, products
• src/services/configure-service.ts — orchestrates scan → gather (interactive or defaults) → write files; conflict detection with --force escape hatch
• src/cli/configure-command.ts — Commander command (--artifact-dir, --environments, --output, --non-interactive, --force)

Prompt service extensions (src/services/prompt-service.ts)

• askApiFilter — multi-select from discovered API names
• askSecretTokenName — token name per secret named value per environment
• askBackendUrl — URL override per backend per environment
• askYesNo — generic yes/no with configurable default

Model (src/models/config.ts) — added ConfigureConfig interface

Non-interactive defaults

• All APIs included in filter
• Each secret: true named value → {#[TOKEN_NAME]#} placeholder (name uppercased, punctuation → _)
• No backend URL overrides written (user edits manually)

Documentation & contracts

• docs/commands/configure.md — full usage docs with onboarding flow diagram
• specs/contracts/cli-commands.md — command contract

[EMaher]

Opted to create prompt files to help create overrides and extraction filter files. See #183