Why we need multiArgs?

@alexander-akait

1. Callback wrapper, like bluebird, wrap callback base api into promise api, optionally accept multiArgs.

Promise.promisify(
    function(any arguments..., function callback) nodeFunction,
    [Object {
        multiArgs: boolean=false,
        context: any=this
    } options]
) -> function

So, I think wrap a callback to .resolveAsync accept multiArgs should be better.

2. Because of opinion 1, for api compact, I think .resolveSync accept Parameters<Resolver['resolveAsync']>, and return Awaited<ReturnType<Resolver['resolveAsync']>>. So, I think wrap a callback to .resolveSync should accept multiArgs.
3. Also resolveRequest contains meta like .descriptionFileData, useful for further sideEffects or else meta parsing