Remove the strict audit-history assertion from test support - #956

…e alternative

The audit log is moving to one record per change (its current state), with the
history of transitions moving to the journal (`Features.JOURNAL_EVENTS`).
`AuditTestHelper#verifyAuditSequenceStrict` / `AuditTestSupport#THEN_VerifyAuditSequenceStrict`
assert an ordered audit *history* (`STARTED, APPLIED, ...`), which no longer
describes what the audit log holds.

**API changes** (`utils/test-util`, published artifact — kept backward
compatible, no hard removal):
- Added `AuditTestHelper#verifyAuditFinalStateSequence` /
  `AuditTestSupport#THEN_VerifyAuditFinalStateSequence`, asserting the final
  state per change (same exclusion rules as `core/flamingock-test-support`'s
  `AuditFinalStateSequenceValidator`: drops `STARTED`, system changes, and
  legacy `_before` snapshots).
- Deprecated the old strict-sequence methods instead of deleting them — they
  still work exactly as before for any existing caller, with a Javadoc pointer
  to the replacement. Actual removal deferred to a future major version.
- `thenExpectAuditFinalStateSequence` / `AuditEntryDefinition` in
  `core/flamingock-test-support` are untouched.

**New: in-memory journal support** (`utils/test-util`), so the STARTED→
APPLIED/FAILED/ROLLED_BACK progression some tests exist specifically to prove
isn't lost when migrated off the audit log:
- `InternalInMemoryJournalEventStore` — in-memory `JournalEventStore`, mirrors
  the shape of `MongoDBSyncJournalEventStore` / `SqlJournalEventStore` /
  `DynamoDBJournalEventStore`.
- `InternalInMemoryAuditStorage#upsertAuditEntry` — current-state upsert
  keyed by changeId, the in-memory counterpart to
  `MongoDBSyncAuditRepository#save`.
- `InternalInMemoryTestAuditPersistence` / `InternalInMemoryTestAuditStore` /
  `InternalInMemoryTestKit` wire the two together, gated by
  `Features.JOURNAL_EVENTS`, exactly like the real audit stores.
- `RecoveryE2ETest` gained a dedicated journal-based test proving the retry
  progression (FAILED → STARTED → APPLIED) survives in the journal even
  though the audit log now only shows the final state.

**Migration of all internal call sites** (21+ files across 11 modules) off
the deprecated API onto the new one:
- "the change ended up applied/failed" → `verifyAuditFinalStateSequence`.
- "the change went through this sequence of transitions" for the
  failure/rollback scenarios → either the journal (where the store supports
  it: MongoDB sync, DynamoDB, SQL, and the in-memory kit) or a final-state
  assertion covering just the outcome (MongoDB reactive, Couchbase, and the
  legacy Mongock importers — none of these have journal support yet).
- `MongoDBSyncJournalFeatureFlagE2ETest` / `DynamoDBJournalFeatureFlagE2ETest`
  updated to use the final-state API for both the flag-on and flag-off cases.

No test's coverage was silently weakened to "it ran" — failure/rollback
progressions land on final-state assertions that still name every terminal
status (e.g. `FAILED` + `ROLLED_BACK` both asserted), and the four stores that
have journal support get an explicit journal-based test proving the dropped
transition history is preserved there.