Documentation GAP for DataKey::Bet Storage

[hman38705]

Description
The DataKey::Bet variant in bets.rs (Line 9) stores participation records in persistent storage. There is no official documentation regarding the TTL (Time To Live) management for these individual bet records beyond the inherited market bump. Individual bet records could potentially expire if a market stays stale for a long time, leading to claim failures.

Requirements and context

• Document the TTL strategy for all per-user storage entries.
• Ensure user claims are protected by explicit TTL bumps during the dispute/resolution window.

Suggested execution

• Fork the repo and create a branch: git checkout -b docs/issue-100-ttl-strategy
• Update comments and implementation.

Implementation changes

• Add explicit documentation to bets.rs and ensure extend_ttl is called on DataKey::Bet.

Test and commit

• Verify that a user's bet record remains accessible 6 months after the initial bet.

Example commit message
docs: document and implement explicit TTL management for bet records

Guidelines

• Comprehensive documentation.
• Timeframe: 24 hours.

[summer-0ma]

@summer-0ma has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi maintainer @ solutions-plug/predictIQ!!!!
I will like to work on this issue!!!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @summer-0ma to this issue.