[backport camel-4.18.x] CAMEL-24622: camel-infinispan - keep completed exchanges for recovery

[gnodet]

Backport of #26115

Cherry-pick of d4539d7 to camel-4.18.x.
Conflicts resolved automatically by backport bot agent.

Conflict resolution

The upgrade guide note was moved from camel-4x-upgrade-guide-4_23.adoc (does not exist on camel-4.18.x) to camel-4x-upgrade-guide-4_18.adoc.

[gnodet]

Clean backport of CAMEL-24622. The fix correctly implements the RecoverableAggregationRepository contract — follows the same pattern as JdbcAggregationRepository (separate completed store keyed by exchange ID, as opposed to the broken previous behavior where scan() returned in-progress correlation keys and remove() deleted the exchange outright).

Key points verified:

• remove() correctly moves the completed exchange from correlation-key storage into recovery storage (camel-recovery:<exchangeId>) instead of deleting it
• confirm() correctly deletes from recovery storage using the prefixed key
• scan() correctly filters to recovery entries only and strips the prefix to return exchange IDs
• getKeys() correctly filters out recovery entries so the aggregation framework only sees in-progress aggregations
• Tests are comprehensive: confirm lifecycle, scan semantics, recover lookup, and a new testGetKeysIgnoresExchangesToRecover test — both embedded and remote
• Upgrade guide note correctly moved to camel-4x-upgrade-guide-4_18.adoc for the backport

Metadata: No milestone set — suggest 4.18.5.

This review was generated by an AI agent, Hermès on behalf of @gnodet.