Tim Deeb-Swihart 049334aa67 Update api-go and sdk-go to allow invalid UTF-8 in protos (#5476) ...

## What changed?
I've upgraded the version of our Go API in order to allow invalid UTF-8
data in our proto strings.

Please review
5cf979058d
only

## Why?
The version of gogo/protobuf we used allowed invalid UTF-8 in strings
which is a violation of the proto3 spec. We were unaware of this until
our new google/protobuf based structs began failing to deserialize data
we'd used previously

## How did you test it?
I added a new end-to-end test to verify that we can create, describe,
and delete a namespace that contains invalid UTF-8 in multiple
attributes

## Potential risks
This is lower risk than commits prior to this as temporal DBs may
already contain invalid UTF-8 data

## Documentation
I adjusted our docs to mention this behavior and the `protolegacy` tag

## Is hotfix candidate?
Yes: this will be going out as part of our 1.23.0 release. In fact, the
release is blocked on it!

---------

Co-authored-by: David Reiss <david@temporal.io>

2024-03-01 23:21:27 +00:00

..

message.go-helpers.pb.go

Clean up protos (#5157)

2023-11-27 18:11:33 +00:00

message.pb.go

Update api-go and sdk-go to allow invalid UTF-8 in protos (#5476)

2024-03-01 23:21:27 +00:00