Need to regenerate records if `matchRequestsBy` changes

Description

If I understand things correctly, having the id hardcoded in the har files makes it so that when matchRequestBy changes no entry is valid. The recordings are in fact still viable but since the id is generated based on matchRequestBy all recordings need to be recreated.

That becomes a big problem when you have a lot of recordings, even the slightest change to matchRequestBy requires to regenerate everything!

I use matchRequestBy to ignore things that are dynamic or may change between two runs. Dates, tokens, some ids, etc... The config is mostly very static but in the case where it needs to change it creates a massive break.

What I would like to see is har files be a pure raw recording of the requests and be independant of the matchRequestBy.

Shareable Source

All entries in har files have this:

{
  "_id": "1f62d02515e4ee31cf40fafc4d01f127",
  "request": ...
}