Generate examples for recordings, run them against specs and open issues about oav

[veronicagg]

I've pushed all the examples I generated to a branch in my fork for reference at https://github.com/veronicagg/azure-rest-api-specs/tree/examples-from-recordings
There should be a folder in the api-version folder called swagger-with-examples, which includes examples and the edited swagger file (if there were recordings available for that service). It's not the idea to merge this code up (at least not now), but to have our generated examples (from .net recordings) available, so I just pushed them to that folder under each spec.

I've run lots of the examples through the validation tool, I've opened issues for many specs. As I extracted some patterns from the issues like "required properties are not coming back in responses" or "properties come back as null which doesn't match the spec'd type", instead of opening issues for all those, I'm writing up some proposals first on how we could resolve those, so we can publish them for service teams.
One of the proposals is already at Azure/azure-rest-api-specs#790

Additionally, we need to think of ways to consolidate the errors in an output that's more readable and less repeated errors, to make it less noisy and more actionable.