fix(plugin-catalog): re-pin provenance-gate to 0.1.3 - #144339

What does this PR do?

Bumps provenance-gate to 0.1.3 (d8ded75deef198694639d8653c1834a26f3b0372).

Three patterns in claims.py backtracked quadratically. All three are fixed, and each one has a
timing test that runs in a subprocess with a hard timeout.

• _KEY_VALUE and _TRAILING_PAREN — a long run of whitespace with no separator made them retry
  from every offset; 1 MiB of spaces took 0.67 s and "a" + 1 MiB + "b" did not finish in 30 s.
  Fixed in 0.1.1 with possessive quantifiers (Hermes requires Python >= 3.11); both finish in
  under 5 ms now.
• _ZH_BRACKETED — six <opener>[^<closer>]*<closer> alternatives with an unbounded middle run, so
  input made only of opening brackets made every start position scan to the end of the string. 40k
  characters took 0.79 s and 160,000 characters took about 12 s. Bounded in 0.1.2; 40k now
  takes 0.008 s.

The only call site passes a slice of at most 120 characters (_WINDOW), so the input that reaches
the gate is unaffected by the third fix: 200,000 random strings of up to 120 characters give
identical results before and after.

0.1.3 adds the timing test for _ZH_BRACKETED and changes no pattern.

Related Issue

No issue. The defects and their fixes live in the plugin repository
(simin-yuan/hermes-provenance-gate, tag v0.1.3); the catalog only needs the pin moved.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• plugin-catalog/provenance-gate.yaml: sha 8813469d… → d8ded75d…, version 0.1.0 → 0.1.3.
  Nothing else in the file changes.

How to Test

1. python scripts/validate_plugin_catalog.py plugin-catalog/provenance-gate.yaml → OK: 1 file(s) valid
2. python scripts/check
3. In the plugin repository at v0.1.3: python -m pytest tests/test_performance.py -q →
   23 passed in 12.7 s. The same test file run against v0.1.1 fails all three bracket cases
   (160,000 characters took about 12 s).

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix (one file, two lines)
• I've run pytest tests/ -q and all tests pass — N/A: catalog data only, no Python in this repository is touched
• python scripts/check passes (the blocking lint and code-health checks CI runs)
• I've added tests for my changes — N/A for a pin; the regression tests ship in the plugin repository
• I've tested on my platform: Windows 11

Documentation & Housekeeping

• I've updated relevant documentation — N/A
• I've updated cli-config.yaml.example if I added/changed config keys — N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
• I've considered cross-platform impact — N/A (YAML pin)
• I've updated tool descriptions/schemas if I changed tool behavior — N/A