chore(deps): bump praxis core to 0.5.5 and pingora fork to 0.9.0

[leseb]

Summary

Bumps the praxis core crates (praxis-proxy*) from 0.5.4 to 0.5.5; since 0.5.5 bumps its pingora fork to 0.9.0, the workspace pins for quixotic-plecostomus-{core,http,proxy} also move 0.8.2 → 0.9.0 to keep a single pingora_core in the graph. Adapts to the three breaking API changes in 0.5.5: FilterPipeline::build_with_chains now takes &InsecureOptions (passed config.insecure_options), AdminEndpointOptions gained a stats field (set to None), and HttpFilterContext gained prior_pre_read_mutations and upstream_reached (added to the test-context constructors). Also regenerates four filter docs where the 0.5.5 schema generator now renders the on_invalid field as its enum type name OnInvalidBehavior instead of inlining the variants.

Related issue

N/A — dependency maintenance bump.

Validation

• Unit tests — cargo test -p praxis-ai-apis -p praxis-ai-filters -p praxis-ai-proxy -p praxis-ai-llmd-ext-proc --lib (1340 passed; the 2 credential_inject file-watcher tests fail identically on the base 0.5.4 — pre-existing macOS fsevents behavior, they pass on Linux/inotify in CI)
• make lint
• make doc

Checklist

• I reviewed every changed line and can explain the change.
• New capabilities include an example config and functional example test. (N/A — no new capability.)
• User-facing behavior and generated documentation are updated.
• Performance-sensitive changes include appropriate benchmark or load-test evidence. (N/A.)
• Commits are signed and include a Signed-off-by trailer.

Breaking changes

None to praxis-ai's public config or behavior; this is an internal dependency bump that adapts call sites to praxis 0.5.5's revised APIs.

[hexfusion]

nice

[nerdalert]

@leseb ty! I kicked a couple of the flakes in the merge-queue job Analyze (rust) and ci-status. If I can squeeze in #980 before a release I would appreciate it! It will get distributed quota in a grid release. Im watching the queue as soon as it hits I will rebase.

Edit: The CodeQL (Analyze (rust)) might not be a flake. A quick poke around returns:

Suggested minimal fix in .github/workflows/codeql.yaml:

  - name: Perform CodeQL Analysis
    uses: github/codeql-action/analyze@cdf488f595d80d6e07e03d4674febd5ab45fa938
    with:
      category: "/language:${{ matrix.language }}"
      upload: ${{ github.event_name == 'merge_group' && 'never' || 'always' }}

Keep the merge_group trigger so CodeQL remains a required merge-queue gate, but skip SARIF upload for the ephemeral gh-readonly-queue ref. Normal PR and main runs will continue uploading results.

[leseb]

@leseb ty! I kicked a couple of the flakes in the merge-queue job Analyze (rust) and ci-status. If I can squeeze in #980 before a release I would appreciate it! It will get distributed quota in a grid release. Im watching the queue as soon as it hits I will rebase.

Edit: The CodeQL (Analyze (rust)) might not be a flake. A quick poke around returns:

Suggested minimal fix in .github/workflows/codeql.yaml:

  - name: Perform CodeQL Analysis
    uses: github/codeql-action/analyze@cdf488f595d80d6e07e03d4674febd5ab45fa938
    with:
      category: "/language:${{ matrix.language }}"
      upload: ${{ github.event_name == 'merge_group' && 'never' || 'always' }}

Keep the merge_group trigger so CodeQL remains a required merge-queue gate, but skip SARIF upload for the ephemeral gh-readonly-queue ref. Normal PR and main runs will continue uploading results.

Thanks, next time feel free to directly push into my branch :)