Support model-type bindings for out-of-proc workers

[liliankasem]

Add support for model-type bindings for out-of-proc workers

• Epic: [Epic] Support SDK-type bindings for out-of-proc workers azure-functions-dotnet-worker#1081
• Related issue: Implement SDK-type binding prototype using new version of ParameterBindingData azure-functions-dotnet-worker#1035

Part of the work to support SDK-type bindings for out-of-proc workers is for the host to bind to ParameterBindingData if a function supports deferred binding. Deferred binding means that instead of resolving binding payloads host-side, it will be deferred so that the worker resolves binding when it gets the invocation request. For example, if a function binds to a BlobClient, instead of creating and passing around a BlobClient, we will use ParameterBindingData to gather all the relevant information the worker would need to create the BlobClient itself (worker-side).

Things happening in this PR:

• Support binding to ParameterBindingData. If a function indicates that it supports deferred binding, we can use ParameterBindingData to get the relevant information from the extension. By setting this as a functions defaultType, we can check extension converters to see if they can provide ParameterBindingData which enables us to bind functions to SDK-types on the worker side.

• A limitation here is that we only support ParameterBindingData and deferred binding for trigger bindings if none of the function's input or output bindings contain an expression (you can read more about why this limitation exists in this issue). Because of this, we first check if the trigger binding "SupportsDeferredBinding". If it does, we check all the attributes for the input and output bindings to see if there are any expressions being used. If an expressions is being used, we set the "SkipDeferredBinding" flag in the function's metadata Properties. We use SkipDeferredBinding later down the line to skip deferred binding for the trigger, meaning we set SupportsDeferredBinding to false. So instead of using ParameterBindingData, we use the defaultType that is evaluated by the WebJobs sdk.

• Update ScriptBindingContext to include Properties prop and a SupportsDeferredBinding prop. In the protobuf, the Binding info was updated to include a Properties map. This map is used by workers to add additional information about a function binding. For this specific feature, the worker will add a SupportsDeferredBinding prop to the Properties map to indicate to the host that a given function supports deferred binding.

• Convert ParameterBindingData to ModelBindingData so that we can send this information of gRPC to workers. ModelBindingData is the gRPC message representation of the WebJobs ParameterBindingData; you can find the protobuf definition for this here

The Azure/azure-functions-dotnet-worker#1081 (comment) has a list of all the PRs related to this feature