Eliminate the workspace-wide `#[ignore = "TODO: re-enable after test isolation issue"]` annotations

[nanaf6203-bit]

Problem Statement

13+ #[ignore]s across staking/tests.rs, bridge/tests.rs, integration_bridge_oracle.rs, prediction-market/src/lib.rs:831, bridge/src/errors.rs:424, bridge_load_tests.rs:226. They all cite "test isolation issue".

Why it matters

Ignored tests mask real regressions — the source of any global-storage leak must be located and fixed.

Technical Context

Locate the shared Lazy/OnceCell/mutable statics that survive between tests. Use ink::env::test::reset() or rebuild test fixtures per test.

Expected Outcome

Zero #[ignore = "test isolation issue"] annotations remain; CI passes both individual and full-workspace cleanly.

Acceptance Criteria

1. All ignored tests re-enabled.
2. cargo test --workspace deterministic.
3. New tests/test_isolation_check.rs enforces that.
4. Test-runtime reduced to < 5 min total.
5. CI diff: pre- and post- run logs identical.

Implementation Notes

Identify offending statics; replace with per-test fixtures.

Files or modules likely to be affected

contracts/staking/src/tests.rs, contracts/bridge/src/tests.rs, tests/bridge_load_tests.rs, plus several others.

Dependencies

None.

Difficulty level

HARD.

Estimated effort

L (~1 engineer-week).

[DevMuhdishaq]

@DevMuhdishaq has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer,

I’m a full-stack developer, and I’d like to contribute to the task. I’ll implement it carefully and efficiently thoroughly understand requirements and edge cases
Communicate promptly about suggestions or improvements. And I will provide regular progress updates and address blockers
Align with project goals through feedback and clarification.

Thank you,

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DevMuhdishaq to this issue.

[drips-wave]

Congratulations, @DevMuhdishaq! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @DevMuhdishaq: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @DevMuhdishaq as part of the Stellar Wave Program's 7th Wave 🥳

😎 @DevMuhdishaq: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.