Limit api versions and metadata v13

[justinrlee]

Two changes:

• Add support for metadataResponse v13 (coming in AK 4.0)
• Intercept ApiVersions responses, and if we see an API key max version not currently supported by Kafka Proxy, rewrite it to the max version supported by Kafka Proxy

Example scenario:

• Client supports Metadata (3) Request/Response v14
• Broker supports Metadata (3) Request/Response v14
• Kafka Proxy only knows how to parse and rewrite Metadata (3) Response v14

Prior to change, this is the workflow (through KP)

• Client submits ApiVersions Request to Broker (passed through KP)
• Broker responds with ApiVersions Response to Client, including Metadata(3) v14 (passed through KP)
• Client sees that both client and server support Metadata(3) v14, and sends Metadata(3) Request v14 (passed through KP)
• Server responds with Metadata(3) Response v14 (intercepted by KP, and dropped on the floor because KP doesn't know how to parse it)

Post this change, this is the workflow (through KP):

• Client submits ApiVersions Request to Broker (passed through KP)
• Broker responds with ApiVersions Response to Client, including Metadata(3) v14
  • KP intercepts ApiVersions Response, sees Metadata(3) v14 in the list of supported API Versions, and rewrites it to Metadata(3) v13 before sending it back to KP
• Client sees that broker 'only' supports Metadata(3) v13, and sends Metadata(3) Request v13 (passed through KP)
• Server responds with Metadata(3) Response v13 (which KP rewrites with new advertised listeners)