[Protocol test enhancement] AWS JSON 1.1/1.0 are missing tests for requestId ser/deser

[rcoh]

This is an especially important feature to test because unlike all other AWS 1.0/1.1 fields, requestId lives in the header:

HTTP/1.1 400 Bad Request
x-amzn-RequestId: LDM6CJP8RMQ1FHKSC1RBVJFPNVV4KQNSO5AEMF66Q9ASUAAJG
Content-Type: application/x-amz-json-1.0
Content-Length: 240
Date: Thu, 15 Mar 2012 23:56:23 GMT

{"__type":"com.amazonaws.dynamodb.v20120810#ResourceNotFoundException",
"message":"Requested resource not found: Table: tablename not found"}

[jasdel]

Similar issue with Request ID in the response document for XML based protocols. Having protocol specific testing that makes it easier for generators to validate correct behavior deserializing the request ID parameter.

[rcoh]

The tricky part of this is that since requestId is unmodeled by smithy, some design work would actually be required to understand how to fit it into the protocol test machinery