Add failure persistence support for regression testing

[BowTiedRadone]

This PR implements failure persistence and regression testing for Rendezvous. When tests fail, the failing seeds and configuration used are now automatically saved to .rendezvous-regressions/, allowing users to replay them on subsequent runs to prevent regressions.

Key additions

• New --mode CLI flag to control test execution: new (fresh tests only), reg (regressions only), or all (both, default)
• Persistent failure storage grouped by test type (invariant/property) with automatic replay
• Failures sorted by timestamp for chronological tracking

Sample failure file
.rendezvous-regressions/ST1PQHQKV0RJXZFY1DGX8MNSNYVE3VGZJSRTPGZGM.counter.json:

{
  "invariant": [
    {
      "seed": 901717247,
      "dial": "example/sip010.cjs",
      "numRuns": 15,
      "timestamp": 1767886534833
    },
    {
      "seed": -1374686468,
      "numRuns": 9,
      "timestamp": 1767886531457
    },
    {
      "seed": 1298457354,
      "dial": "example/sip010.cjs",
      "numRuns": 20,
      "timestamp": 1767883389583
    },
  ],
  "test": [
    {
      "seed": 1656313995,
      "numRuns": 6,
      "timestamp": 1767886553125
    },
    {
      "seed": 64830639,
      "numRuns": 11,
      "timestamp": 1767886546477
    },
    {
      "seed": 1593583466,
      "numRuns": 3,
      "timestamp": 1767886542907
    },
  ]
}

This brings Rendezvous closer to production-grade fuzzing by ensuring discovered bugs stay caught, while improving internal code organization and maintainability.

Closes #130.

[BowTiedRadone]

Since --mode is now binary and --mode=new doesn't have any effect, a --regr option would be more suitable. To update.

[wileyj]

definitely nit-picky - but if this dash line is being copied/pasted many times for output, wouldn't it make sense to have it as a variable?

[wileyj]

maybe it's time to think about some form of standardized logger (or customizing an existing one?)

[BowTiedRadone]

@wileyj Great suggestion! Definitely makes sense to turn into a variable. Regarding logging, we have a custom event-based logger in place.

[wileyj]

full disclosure: i did something like this once, and went a bit overboard. when i was refactoring, it was a nightmare to replace all the ********************* lines with the new separator 😆