Prepare for v1.16.0

[jhump]

Below are draft release notes for this release.

---

v1.16.0

This release is mostly bug fixes but also reconciles connect-go with recent updates to the specification regarding mapping of RPC error codes to/from HTTP status codes (see connectrpc RFC 003)

What's Changed

Other changes

• Revise RPC error code <-> HTTP status code mappings per latest changes to spec by @jhump in Revise code mappings per latest changes to spec #706

Enhancements

• Only send a grpc-status-details-bin trailer in the gRPC protocol if the error has details by @bhollis in Only send a serialized Status in the gRPC protocol if it has details #713

Bugfixes

• Fix ErrorWriter IsSupported check to report false on ambiguous content-type and options indicate connect protocol version header is required by @emcfarlane in Fix ErrorWriter IsSupportedCheck with required connect protocol option #700
• In Connect unary protocol, fallback to code based on HTTP status if unable to deserialize code from JSON body by @jhump in In connect unary protocol, fallback to code based on HTTP status if unable to deserialize it #702
• Fix ErrorWriter to recognize protocols, even if content-type indicates unrecognized codec by @emcfarlane in Fix ErrorWriter to be codec agnostic #701
• Fix some places in the framework that weren't correctly recognizing and returning context-based error code (e.g. "canceled" or "deadline_exceeded") by @jhump in Update a couple of more places where we should return a context error if there is one #709
• Use "unimplemented" code for stream cardinality violations by @jhump in Use "unimplemented" code for cardinality violations #712
• Restrict which metadata in an error can be propagated into response metadata by @emcfarlane in Restrict metadata headers in error propagation #711

New Contributors

• @bhollis made their first contribution in Only send a serialized Status in the gRPC protocol if it has details #713

Full Changelog: v1.15.0...v1.16.0