Add offchain worker to prune transaction receipts after configurable delay, with API discovery and compatibility research

Summary

Introduce an offchain worker responsible for pruning transaction receipts after a configurable delay period (e.g., 180 days). This helps manage storage growth by systematically removing outdated receipts.

Motivation

Transaction receipts can accumulate over time, leading to increased storage requirements. Providing an automated, offchain mechanism to prune receipts after a set duration will ensure disk usage remains manageable and allow node operators to control retention according to their requirements.

Proposed Solution

• Implement an offchain worker that triggers on a regular schedule (e.g., daily/weekly).
• The worker should delete/prune transaction receipts older than a configurable retention period (default: 180 days).
• Make the retention period configurable via node settings.
• Ensure that the pruning process does not interfere with consensus or other core operations.
• Add nodeinfo or similar diagnostic flags so that API/SDK users can programmatically recognize if pruning is active/enabled (to avoid or clarify historical data queries).

Areas for Research

• Analyze which public APIs, SDKs, or exposed interfaces rely on long-term receipt availability.
• Identify any breaking changes or compatibility impacts.
• Consider compatibility requirements for ecoystem tools that may expect complete historical receipts.

Acceptance Criteria

• Offchain worker is added to the node.
• Transaction receipts older than the set retention period are pruned automatically.
• The retention period can be configured in the node settings.
• Proper logging/metrics are added to monitor pruning events.
• Node exposes a flag for pruning status/discoverability in its API.
• Documentation and release notes call out affected/broken interfaces and steps/incidents for migration or forward-compatibility.
• Thorough testing to ensure no unintended data loss or consensus impact.

Additional Context

This feature would allow node operators to optimize storage usage and manage long-term growth of transaction receipts efficiently. It also enhances transparency for API consumers querying historical transaction data when pruning is enabled.