feat(codegen): support custom grain-call return types
Proposal
Allow grain-call return types to register the invokable base used by generated proxies without adding return-type-specific logic to Orleans. InvokableBaseTypeAttribute can now be applied to the return type or at assembly scope, so an adapter assembly can connect independently owned return types, proxy bases, and invokable bases.
Resolution semantics
Mappings are resolved deterministically with exact closed registrations before open generic registrations, then by source precedence: method override, return-type registration, assembly adapter, and proxy default. A compilation-scoped resolver is shared by the analyzer, generator, and incremental interface model. Discovery sorts current and referenced assemblies, coalesces identical registrations, and reports stable diagnostics for conflicts, attempts to replace built-ins, inaccessible or incompatible bases, generic arity and constraint failures, invalid return-value initializer signatures, and bases which generated requests cannot construct.
Generics and compatibility
Open generic mappings are normalized and constructed from the grain method return type after arity and recursively substituted constraint validation. Existing proxy defaults and method-level overrides retain their behavior, including ReturnValueProxy initialization and generated-activator construction. Invokable bases must expose an accessible parameterless constructor or a generator-compatible accessible [GeneratedActivatorConstructor] path. The adapter mechanism remains in the serialization/code-generation layer and adds no Orleans Core or provider dependency.