Added simplified request and response body matching in case of multiple examples.

[VShingala]

Overview

This PR simplifies the logic to generate the request examples in case when multiple request and response body examples are mentioned in definition.

What's changing?

We've removed functionality where if example was used in one response code, it wasn't being used in other response code examples. This was intended before but it creates a lot of confusion to users.

We are also changing how the matching of request and response bodies happens to create examples in below order.

• Check if request and response body have examples with matching keys. (Example Key)
• If we find any matching, we'll create example with matching keys (request and response example) and ignore other examples with non matching keys.
• If no matching could be found, we'll switch to matching based on Positions. i.e. First response example with first request example, second response example with second request example and so on.
  • If there are req/res examples left for which positional match could not be found, then we'll default to using the first example of counter part.

[webholik]

@VShingala What's the reason for doing this? The request and response can be of different types. Why give preference to same content types?

[VShingala]

@webholik Yes, we only give preference to same content type if available. Reasoning is, It makes better example if both request and response body are in same content type.

Although, if same content type is not present we do pair different content types as well.