[BUG] Increase admin max header data response size

[katrogan]

Describe the bug
When admin returns a dump of error logs in a response this can exceed the gRPC trailing metadata limit which obscures the original source of the error.

Expected behavior
Admin should be able to propagate error messages fully to callers.

Flyte component

• Overall
• Flyte Setup and Installation scripts
• Flyte Documentation
• Flyte communication (slack/email etc)
• FlytePropeller
• FlyteIDL (Flyte specification language)
• Flytekit (Python SDK)
• FlyteAdmin (Control Plane service)
• FlytePlugins
• DataCatalog
• FlyteStdlib (common libraries)
• FlyteConsole (UI)
• Other

To Reproduce
Steps to reproduce the behavior:

1. Have a workflow with a task that outputs a reaaaaally big schema. Add a subsequent task with a different, but also long schema definition that consumes the output of the previous task.
2. Attempt to register the workflow
3. Be confused by the response

flytekit.common.exceptions.scopes.FlyteScopedSystemException: <_Rendezvous of RPC that terminated with:
status = StatusCode.RESOURCE_EXHAUSTED
details = "received trailing metadata size exceeds limit"
debug_error_string = "{"created":"@1605080075.767410113","description":"Error received from peer ipv4:XX.Y.ZZ.12:443","file":"src/core/lib/surface/call.cc","file_line":1041,"grpc_message":"received trailing metadata size exceeds limit","grpc_status":8}"

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
Flyte component ALL

• Sandbox (local or on one machine)
• Cloud hosted
  • AWS
  • GCP
  • Azure
• Baremetal
• Other

Additional context