Add regression test for protocol admin address unchanged after fee config update

[Chucks1093]

Summary
Updating the fee config should not modify the protocol admin address. A regression test that reads the admin address before and after a fee config update confirms the admin field is not accidentally overwritten by the config update logic.

Scope

• add a regression test that records the protocol admin address before a fee config update
• perform a fee config update
• assert the admin address is identical after the update

Acceptance Criteria

• the protocol admin address is unchanged after a fee config update
• the test fails if the admin address changes
• the test uses the read-only admin address method for both reads

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[Dannyswiss1]

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

can I jump on this?

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

[Bigdaddyobamo]

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

Let me quickly attend to this issue. I can add the regression test around the fee config update, read the protocol admin before and after, and make sure the test fails clearly if the admin address ever changes. I can start immediately and deliver a tested PR today.

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

[drips-wave]

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

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