Fix RFC 6570 reserved expansion for {+name} resource-path params

[mhsdef]

What

Path params expressed as {+name} in a discovery template use RFC 6570 reserved expansion — the value is a resource name like projects/p/locations/l/processors/x whose / separators must survive into the URL. The generator was detecting these with:

String.ends_with?(path, "{#{wire}}")

which only matches the simple {name} form — never {+name}, and misses mid-path forms like {+name}:process. So every reserved param fell through to the simple, slash-encoding encoder, producing URLs like:

/v1/projects%2Fp%2Flocations%2Fus%2Fprocessors%2Fabc:process

which Google can't route. This broke core Document AI processing (process, batchProcess, operations polling) and async Vision operations polling in any consumer (e.g. Dozer), shipped in 0.1.0.

Fix

Detect reserved expansion by its actual marker — {+wire} in the path — and pick the encoder accordingly:

• {+name} / {+parent} → preserve / (~73 endpoints across the three clients: Doc AI processors/operations, Vision files/operations, etc.)
• simple {object} / {bucket} → percent-encode / (GCS object names must be encoded)

This also removes the old Storage-specific special-case for object/destinationObject, which was a band-aid over the same broken heuristic — the corrected rule handles it naturally.

Blast radius

Encoder-only change. Regenerated all three clients from the cached discovery specs (deterministic; diff is purely URI.encode predicates + formatting reflow). No model or API-surface changes.

Verification

• Generator unit tests updated to lock in the corrected semantics (a {+name} param is reserved; a simple {object} is not) — the regression test that would have caught this. mix test → 60 pass.
• Drove each regenerated client with a capture adapter:
  • Doc AI process → …/v1/projects/p/locations/us/processors/abc:process ✅ literal slashes
  • Doc AI operations.get → …/v1/projects/p/locations/us/operations/123 ✅
  • Vision operations.get → …/v1/operations/abc123 ✅
  • Storage objects.get("bucket", "folder/sub/file.pdf") → …/o/folder%2Fsub%2Ffile.pdf ✅ still encoded (GCS-correct)

Clients bumped to 0.1.1. Publish is manual (Hex passphrase/2FA).