Clients typing inconsistency

[gullmar]

ActorClient's methods start and call have as a first parameter input?: unknown. The same methods in TaskClient have input?: Dictionary. This is inconsistent, and allows passing an input with the wrong type when using ActorClient.

[Pijukatel]

Hello, the type Dictionary seems to be too restrictive. I tried a bunch of inputs, and they actually work even though some of them would not be allowed by the type.

...
// Type compliant with Dictionary, works fine with API
apifyClient.actor(someActorId).start({ a: "whatever" });
apifyClient.actor(someActorId).start({ a: 1, b: 2 });
apifyClient.actor(someActorId).start(undefined);

// Not type compliant with Dictionary, works fine with API
apifyClient.actor(someActorId).start(null);
apifyClient.actor(someActorId).start([1,2,3]);
apifyClient.actor(someActorId).start("x");
apifyClient.actor(someActorId).start(Buffer.from("asda", "utf-8"));
apifyClient.actor(someActorId).start(apifyClient);

// This fail at the client level without calling API
apifyClient.actor(someActorId).start(Symbol('bla'));
apifyClient.actor(someActorId).start(true);
apifyClient.actor(someActorId).start(1);

[l2ysho]

Also ActorStandby missing some parameters

export interface ActorStandby {
    desiredRequestsPerActorRun: number;
    maxRequestsPerActorRun: number;
    idleTimeoutSecs: number;
    build: string;
    memoryMbytes: number;

-> disableStandbyFieldsOverride?: boolean; <-
-> shouldPassActorInput: boolean; <-
}