Add automated parity validation between testnet and mainnet configuration

[Emmyt24]

Description

Add a check that compares testnet and mainnet configuration shape (same keys/feature flags set) so environments do not silently drift apart.

Requirements and context

Handle network failures gracefully with retries/backoff where appropriate, avoid leaking credentials, and add integration tests using mocked external services. Update configuration docs and keep coverage at target.

Suggested execution

Create a feature branch using the convention:

feat/integration-env-parity-check

Implement changes

• Compare the set of configuration keys/flags across environments.
• Flag keys present in one environment but missing in the other.
• Allow an explicit allowlist for intentional differences.
• Add tests for in-parity and drifted configurations.

Test and commit

Run the test suite. Document the allowlist mechanism in the PR.

Example commit message

feat(integration): add testnet/mainnet config parity check

Guidelines

• Follow the existing code style, linting rules, and module conventions already present in the repository.
• Keep the change focused and reviewable; avoid unrelated refactors in the same PR.
• Write clear, descriptive commit messages using the Conventional Commits format.
• Ensure all CI checks pass (build, lint, type-check, tests, coverage) before requesting review.
• Open a pull request against the default branch, link this issue (Closes #<id>), and describe what you changed and how you verified it.
• Be responsive to review feedback and keep the PR scope aligned with this issue.

[emickwrld]

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

Hi, I’m a smart contract and a full-stack web developer, I have read through the issue and it’s something I’m capable of doing. Please assign me this work.

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

[karanjakevin39-collab]

@karanjakevin39-collab has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Can i work on this issue ?

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

[Onomebello]

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

Hello i would like to work on this issue

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

[drips-wave]

Congratulations, @Onomebello! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Onomebello: 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 🌊