feat(options)!: pf-4119 programmatic, CLI, experimental registry

[cdcabrera]

What is it?

• feat(options)!: pf-4119 programmatic, CLI, experimental registry
  • index, annotations, pass experimental options for setOptions
  • options, registry driven options for programmatic, CLI, experimental
  • options.parser, breakout CLI and programmatic parsers
  • options.context, confirm experimental options
  • options.defaults, experimental options list for use tracking
  • options.helpers, kebabToCamel helper
  • server, log warnings for experimental option use
  • e2e, minor typing, parser imports

Notes

• only base work. this base does not include any experimental options being activated
• includes a refactor of how args are passed through the cli which in turn includes an enhancement where we can now parse multiple options as a list, for example --tool one --tool two --tool three
• potential follow up skill add, cdcabrera@32a1389

BREAKING CHANGE: PfMcpOptions is now limited to the supported options registry;
extra keys passed to start() are ignored. Previously, any DefaultOptions field
could be supplied programmatically.

This change centralizes option metadata and ensures that only supported,
validated configurations reach the server instance.

To migrate:

• Ensure all keys passed to start() match the PfMcpOptions interface.

Check the work

Implements an experimental flag here, cdcabrera@39cc297

1. Update the NPM packages with $ npm install
2. $ npm run build
3. $ npm run test:integration
4. confirm the e2e checks come back clean. the related e2e is located in stdioTransport.test.ts

Updates issue/story

closes #183 pf-4119

related #182

[cdcabrera]

One final round of testing with the next set of commits for #141 and #182

[cdcabrera]

Review found an optimization... investigating