Protocol:

1. Command name: UpsertWorkflowTypedSearchAttributes
2. Payload is the same as for the regular (untyped) search attributes, except the value is now typed. This is the regular associate array map[string]*struct, but the value (*struct) is typed. It is not contains two fields: type (string) and value (int, bool, float, string, []string).
   Example:

{
"key1": {
	"type": "float64",
        "operation": "unset"
},
"key2": {
	"type": "bool",
        "operation": "set",
	"value": true
	},
"key3": {
	"type": "keyword_list",
        "operation": "set",
	"value": ["1", "2"]
	}
}

Where: "key1,2,3" are search attribute names with nested values and corresponding types.

Types can be:

1. bool: values: true, false (json native).
2. float64: values: 1.2, 2.5 (json native).
3. int: values: 1,2 (json native)
4. keyword: values: string, native.
5. keyword_list: values: array of string, native.
6. string: values native string.
7. datetime: values: time in RFC 3339 format. Will be parsed on the RR side.

Payload may have any number of variations of these types.

When the type or value can't be parsed correctly, RR will send the warn-level log and continue parsing the next field.

Operations can be:

1. set - to set a SA. Used by default if not set (field).
2. unset - to unset the SA.