Functions Host V3 and Nodej.s Worker V2

[mhoeger]

v2.x branch currently (see changes here):

• introduces "v1WorkerBehavior" flag which reverts everything "[breaking]"
  • In the future: we want to have the functions host send over specific breaks to opt out of
• [breaking] throws on Node.js v8, keeps 8 binaries for V2 host compat
• changes worker version to 2.0.0
• [breaking] does not duplicate http payload in context.bindingData
• [breaking] fixes HTTP output through context.done(null, res) and $return is not handled correctly #228 (handles http output correctly on context.(null, { body: "hello" });
  • TODO: [Worker V2] Fail gracefully on invalid http output #268
• [breaking] fix camelCase of timer trigger object: camelCase Timer Trigger object #188
• [breaking] fix type conversion of code like return { outputBinding: info, outputBinding2: info };: Node: Blob output binding should support passing a Buffer #232
• [breaking] consume "TypedDataCollection" Event hub, Binary datatype and Cardinality many #262
• add unspecified for http => Introduce SameSiteMode.Unspecified equivalent in 3.x azure-functions-host#4890 (comment)

TODO:
- remove Node.js v10 support?

• [breaking] in host and worker, make sure http payload "as raw" as possible
• [breaking] rawBody http property should not be a UTF-8 string for byte data (rawBody http property should not be a UTF-8 string for byte data azure-functions-host#4475)

In the future:

• explore options for bugs with protobuf.js and windows (Issue 1303, Issue 1275)
  • protoc or just default Linux and accept Windows bugs? Probably document windows bugs
• do correct fix for camelCase camelCase Timer Trigger object #188 (potentially add .proto)

[ColbyTresness]

Also note we need a change on the platform to auto upgrade customers node versions if they move to V3 and are on an older Node version (8, for instance). They should be notified of this change.

[mhoeger]

Closed with Azure/azure-functions-host#5335