feat: add append-only holder registry per creator key (issue #831)

[meem08]

• Reworked DataKey to store Vec per creator (holder_registry)
• Added get_holder_registry view returning full list
• Derived has_ever_held and get_historical_holder_count from registry
• TTL bumped on every read and write (extend_key_ttl_to_full_window)
• Circuit breaker fix: read CIRCUIT_BREAKER_THRESHOLD from storage, default 30%
• Pre-existing formatting fixes to prelaunch_auction and staking_reward_claim tests

Summary

closes #831

Testing

• cargo fmt --all -- --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace

Checklist

• Linked issue or backlog item
• Added or updated creator-keys unit/integration tests for every changed contract behavior, including failure paths for new or reachable ContractError variants
• Ran cargo fmt --all -- --check, cargo clippy --workspace --all-targets -- -D warnings, and cargo test --workspace, or explained exactly why a command was not run
• Reviewed persistent storage changes against docs/storage-key-invariants.md; any storage layout change includes a migration/backward-compatibility note
• Confirmed event names, topic order, payload field order, and field meanings remain compatible with docs/contract-event-conventions.md, or documented the breaking change and versioning plan
• Updated docs for any changed public contract interface, read-only method, event schema, storage behavior, fee logic, or deployment workflow
• Scope stays limited to one contract concern and does not include unrelated formatting, lockfile, generated artifact, or dependency changes

[drips-wave]

@meem08 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Chucks1093]

❌ CI Failed — verify (Contracts CI)

The verify check is failing on this PR.

Likely causes:

• Compile error from unresolved identifier or missing import after merge
• cargo fmt not run — formatting diff causes CI to fail
• Clippy lint warnings treated as errors (deny(warnings))

Steps to fix:

1. Run cargo build locally and fix any errors
2. Run cargo fmt --all and commit the result
3. Run cargo clippy -- -D warnings to catch any lint issues
4. Push — CI will re-run automatically