servicecomb由 1.X升级至 2.X 后InvokerUtils.syncInvoke(）无法适配场景咨询

业务网关implements InvocationHandler，在反射中做rpc调用，但是升级servicecomb后 InvokerUtils.syncInvoke方法参数变了，这个有啥办法处理Object[] args 转成 swaggerArguments，尝试过将method中parameters的name做key，但是没发保证arg[]顺序和method入参一致

例如：
public class Invoker implements InvocationHandler {
@Override
public Object invoke(Object proxy, Method method, Object[] args) {
Object response = InvokerUtils.syncInvoke(microserviceName,
microserviceSchemaId, microserviceOperationId,args);
}
}

Start by comparing the ServiceComb 1.x and 2.x InvokerUtils.syncInvoke signatures and tracing the provided InvocationHandler example. Determine how the Object[] args should map to the 2.x swaggerArguments while preserving the method parameter order. Done means the supported invocation path is documented or corrected with a verified argument mapping.

Written by the indexing model from the issue text.