Improve Errors for Request Matching Failures

[akosyakov]

Currently, when a request does not match a recorded interaction in the cassette, go-vcr simply reports a mismatch without providing detailed information about why the request failed to match. This makes debugging difficult, especially when subtle differences exist in headers, body content, or query parameters.

It would be helpful if the default matcher could provide better error messages, such as:

Which headers are missing, unexpected, or have different values
Differences in query parameters or their order
If the request body differs, highlight the difference

[dnaeon]

Hey @akosyakov ,

Not sure when and whether I would find spare time to work on this one, but I'd be happy to review any PRs with such features, thanks!