IS-05 v1.1 transport_params schemas don't validate as intended

[garethsb]

The mechanism by which we introduced the transport parameters for the additional transports' has had the unfortunate side-effect of making unexpected instances validate.

E.g. the following PATCH /single/receivers/{receiverId}/staged request body validates right now

{
  "transport_params": [
    {
      "destination_port": "foo"
    }
  ]
}

That's because although the transport params don't pass the RTP params schema, it does pass the WebSocket params schema, because the schemas don't prohibit additional properties (and have no required properties because it's valid to stage as few params as you like).

Fix PR on the way...