The GoRPC client generator was creating variable name conflicts when service method parameters had the same name as internally generated variables. The generator uses fixed variable names like 'req' for request structs, but if a method parameter was also named 'req', it would create a naming conflict in the generated code.

Example of the conflict:

func (tsc *ServiceGoRPCClient) GetUser(req int) (name string, clientErr error) {
    req := ServiceGetUserRequest{Id: req}  // ← CONFLICT!
    //     ↑ variable name    ↑ parameter name
}

Changes:

• Change parameter naming from field names to indexed arguments (arg_0, arg_1, etc.)
• Add context filtering to prevent context.Context from being included in GoRPC requests
• Add isContext() method to Value type for context detection
• Ensure parameter names never conflict with internal generator variable names

This ensures that:

• Generated GoRPC client code compiles without variable name conflicts
• Method parameters use unique names that don't clash with internal variables
• Context parameters are properly filtered from request structs
• Generated code is robust regardless of service method parameter names

Fixes compilation errors when service methods have parameters with names that conflict with internally generated variable names (like 'req', 'response', etc.).