Make callHttp accept one options object argument

[hossam-nasr]

Following the lead of #415 and #429, this PR also switches the context.df.callHttp() on orchestration contexts from using explicit arguments to using one options argument for all parameters, following the lead of popular frameworks like axios

Before (actual sample from our docs here):

const restartResponse = yield context.df.callHttp(
        "POST",
        `https://management.azure.com/subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.Compute/virtualMachines/${vmName}/restart?api-version=${apiVersion}`,
        undefined, // no request content
        undefined, // no request headers (besides auth which is handled by the token source)
        tokenSource
);

After:

const restartResponse = yield context.df.callHttp({
        method: "POST",
        url: `https://management.azure.com/subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.Compute/virtualMachines/${vmName}/restart?api-version=${apiVersion}`,
        tokenSource,
});

Changes that were made in this PR:

• Now accepting an options argument inside of 5 different arguments
• Renamed uri to url
• Renamed content to body (I'm assuming that's what "request content" meant?)

If there are other (breaking) changes we want to make to the callHttp API, now is the time to call them out. For example:

• Do we want to follow @azure/functions's lead and accept an undici HttpHeaders type for headers parameter instead of an object of strings?
• Do we want to rename the asynchronousPatternEnabled argument? It always felt like a confusing name to me, but this is the same the extension uses.