feat: Extract cadence-caller-type from headers at services inbound boundaries

[fimanishi]

What changed?
Extract CallerInfo from yarpc headers at all service inbound boundaries using middleware and add it to the context.

#7654

Why?
We want to use caller type that may be present in the caller info, and other caller info fields to be added, on services like frontend and history. They will probably not be needed in matching and they will probably not be added to the headers at that point, making this a noop.

The performance impact is around 300ns as per this estimation:

1. Header extraction (GetCallerInfoFromHeaders):
   - yarpc.CallFromContext(ctx) - fast map lookup
   - call.Header(CallerTypeHeaderName) - fast string map lookup
   - ParseCallerType(string) - simple string comparison
   - Cost: ~100-200ns
2. Context wrapping (ContextWithCallerInfo):
   - context.WithValue() - creates new context wrapper
   - Cost: ~50-100ns
3. Total per request: ~150-300 nanoseconds (0.15-0.3 microseconds)

How did you test it?
Unit test and local test running cadence locally.

Potential risks
As mentioned above, some performance issue that may represent around 0.002-0.03% of total request time

Release notes

Documentation Changes

[gitar-bot]

Code Review ✅ Approved

Well-designed middleware implementation with clean refactoring from pointer to value semantics. The removal of yarpc dependency from types package improves testability. Comprehensive test coverage follows project conventions.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}