Add freeze position toggle on user key holdings panel

[Chucks1093]

Summary

Add a self-custody freeze toggle on each key holding in the user's portfolio, allowing users to freeze and unfreeze their positions with a confirmation step.

Scope

• Freeze toggle button on each holding in the portfolio table
• Confirmation modal explaining freeze consequences before applying
• Frozen badge on holdings that are currently frozen
• Buy and sell buttons disabled with tooltip when position is frozen
• Unfreeze confirmation modal before releasing the freeze

Acceptance Criteria

• Freeze confirmation modal shown before applying freeze
• Frozen holdings show distinct badge in portfolio table
• Buy and sell buttons disabled with explanatory tooltip on frozen positions
• Unfreeze confirmation modal shown before releasing
• Freeze state fetched from API and reflected correctly on load

ETA

12 hours

[Damilorlar]

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

I would love to work on this project

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

[mayborn005]

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

Hello @maintainer, I'd love to work on this issue. I'll keep the implementation simple, clean, and well-tested.

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

[abdulrahmanj383-creator]

@abdulrahmanj383-creator has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I’m interested in taking on this task and contributing meaningfully to the project. I’ve reviewed the requirements and believe I can work through the task carefully, communicate clearly, and deliver a solid implementation within the expected timeframe.

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

[CollinsKRO]

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

Hi maintainer, I can fix this pls assign.

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

[mysterio123865]

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

Pls kindly assign

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

[Benedict315]

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

Hello please assign me to this issue

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

[drips-wave]

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

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

[mayborn005]

@accesslayerorg The implementation for #936 is already present on the required dev branch. Previous PR #950 was automatically closed because it targeted main; GitHub reports the contributor branch and dev are now identical, so there are no new commits to raise without duplicating the work.

[mayborn005]

@accesslayerorg The implementation is already present on the required dev branch. Previous PR #950 was automatically closed because it targeted main, and GitHub reports the contributor branch and dev as identical, so there are no new commits available for a valid replacement PR.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@mayborn005's PR #1006 was approved and merged by @Chucks1093.

🏆 @mayborn005: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,089 total points). Track your full progress on GrantFox.

👏 Great work, @mayborn005! Keep contributing to accesslayerorg.

[drips-wave]

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

😎 @mayborn005: 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.