Resolve local OpenAPI URI-fragment pointers

[rudycelekli]

Description

Local OpenAPI parameter references now decode URI fragments and traverse array entries with the same JSON Pointer resolver used for external documents. Invalid negative or noncanonical array indices remain unresolved instead of selecting unintended parameters; dictionary keys retain their literal semantics.

How has this been tested?

• Added native regression tests that fail against develop ae0268771f76 and pass with this change.
• Ran the regression and adjacent repository tests: 293 passed in 0.84s.
• Ruff lint/format and git diff --check pass.
• Tests use repository source with declared dependencies and isolated temporary settings; no live provider credentials or data services.

Full provider integrations were not run.

Additional compatibility checks: the combined production changes pass the full core suite (2,270 tests, 36 skipped, 184 subtests). The canonical CLI suite passes 2,241 tests with one existing backend test failure reproduced on unchanged develop. Individual native regression and adjacent tests pass; changed production files and new regression tests pass Ruff and ty. Existing OpenAPI test typing diagnostics also reproduce on unchanged develop. No live data-provider integrations were exercised.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}