[FlightRPC] Explore using HTTP status codes as the canonical status definition

[lidavidm]

Describe the enhancement requested

We currently ad-hoc map through some of gRPC's status codes and awkwardly map to Arrow status codes (in C++) or a custom exception (in Java). Ideally we'd always expose exactly a consistent set of Flight status codes (this makes it easier to predict behavior across languages, at maybe the cost of a little convenience for someone only working in a single language)

Also see

• [Docs][FlightRPC] Document Flight error status mappings #34544
• [Flight] Flight error status for quota exceeded #35888
• https://github.com/grpc/grpc/blob/master/doc/http-grpc-status-mapping.md
• https://github.com/cloudendpoints/esp/blob/1b02c011f071a8d400dbbbc08b512700b69ae519/src/api_manager/utils/status.cc#L287-L327
• GH-36512: [C++][FlightRPC] Add async GetFlightInfo client call #36517 (comment)
• https://buf.build/googleapis/googleapis/file/main:google/rpc/code.proto

Component(s)

FlightRPC

[lidavidm]

Googleapis already defines canonical mappings between gRPC and HTTP status codes. However, these are lossy in both directions. Given that, I'd rather stick with the canonical gRPC codes for Flight since we already use them, and we should just update the Flight codes to be 1:1 with gRPC (e.g. to fix #35888).

We could define our own symmetric mapping, but I'd rather not risk doing something that would confuse people who also want to use existing gRPC infrastructure (e.g. HTTP proxies).