feat(common): add TypeInfo converter hints

[THardy98]

What was changed

Extended TypeInfo<T, D> with an optional ConverterHint<D> and added optional hint parameters to payload-converter serialization methods. Payload converters may expose the experimental validateConverterHint method, and CompositePayloadConverter uses it to select or validate the converter that receives a hint.

The TypeInfo conversion helpers now forward hints after applying transfer conversion. This is PR 2 of the stack and depends on #2250; Nexus operation integration follows separately.

Why?

Transfer conversion is sufficient for formats such as JSON, but some payload converters require format-specific runtime information. Protobuf deserialization, for example, needs the message type in addition to the decoded bytes.

Conversions without a hint retain their existing best-effort behavior. This API is experimental and requires no rollout or manual steps.

Checklist

1. Closes: N/A

2. How was this tested: Common build and all 38 Common tests; focused JSON transfer conversion and Protobuf converter-hint coverage; ESLint; Prettier; and ts-prune.

3. Any docs updates needed? No; documentation will accompany the completed experimental API.

[chris-olszewski]

It would be nice to have a test that exercises a TypeInfo with both a transfer type converter and a converter hint.

[chris-olszewski]

Should D be passed as a generic to TransferTypeConverter so the mapping function typings line up with the type hint?

[THardy98]

Yeah I think so - i've added in the last commit.

[chris-olszewski]

Should we restrict converter hints to ones that are branded with the expected type? I can't think of a reason we would want to be more permissive here.

Suggested change

	fromPayload<T>(payload: Payload, context?: SerializationContext, hint?: ConverterHint): T;
	fromPayload<T>(payload: Payload, context?: SerializationContext, hint?: ConverterHint<T>): T;

[THardy98]

Yup - added in last commit