Populate WorkerMetadata in WorkerInitResponse message

The protobuf has been updated to include a WorkerMetadata property within the WorkerInitResponse message. The worker should include WorkerMetadata when sending the WorkerInitResponse to the host.

PR for reference on how to fill in the fields.

You will need to pull in the latest protobuf version first (this doc may help).

message WorkerMetadata {
  // The runtime/stack name
  string runtime_name = 1;

  // The version of the runtime/stack
  string runtime_version = 2;

  // The version of the worker or worker SDK
  string worker_version = 3;

  // The worker bitness/architecture
  string worker_bitness = 4;

  // Optional additional custom properties
  map<string, string> custom_properties = 5;
}

[Francisco-Gamino]

@liliankasem – The next deployment (which starts January 3rd) of the PowerShell worker 7.2 will have this fix.

[Francisco-Gamino]

@liliankasem - In order to populate the language worker RuntimeVersion, we need to initialize the worker to use the PowerShell SDK (either 7.2 or 7.0). Currently, this initialization takes place in the first ProcessFunctionLoadRequest once we know the functionAppRoot and whether the customer has enabled Managed Dependencies. However, to complete this work item, we need to move the initialization of the worker to ProcessWorkerInitRequest. After this change, we need to test in prod to make sure no regression are introduced. I will discuss with this with the team in our next sync up and provide a new ETA.

/cc @AnatoliB @michaelpeng36