Re: ApiVersionsResponse writes apiKeys prepended with two bytes instead of one byte.

There is an appended `0x00` after the correlation ID if the response header version is v1 because of the tag buffer. While this is valid, the client does not seem to honor this response. With the response header version set to v0, the payload is honored correctly by the client. By that, I mean, the

ApiVersionsResponse writes apiKeys prepended with two bytes instead of one byte.

Hi, I am implementing broker as a hobby project. Here is the high level flow. 1. Set up a response header with correlation ID and header version (1). 2. Create an `ApiVersionCollection` and add APIs. For now, I have added only two - `PRODUCE` and `METADATA` with min, max versions and no tagged fie