fix: ensure unstake max will unstake all user shares

[nickewansmith]

Description

1. This PR addresses a bug where when unstaking entire balance staked causes 1 share to be left in the vault that cannot be unstaked from the UI.
2. The solution is for mobile only and is a quick fix, note that the issue currently exists in portfolio as well and will need to be fixed properly. We solve the issue by calling the getShares contract method to get the total user shares instead of converting the total assets into shares with the convertToShares contract method. We add the interface for the getShares contract method on the fly as it is not part of the contract abi in the stake-sdk where we get the contract instance from.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/STAKE-867

Manual testing steps

1. Stake some amount of ETH or have some ETH staked already
2. Unstake All of the ETH
3. When the transaction is successful, there should be no ETH listed for the Staked Ethereum asset value. It should be exactly 0 and not < .0001
4. If there is an account that has 1 share left, it should now be able to exit that 1 share.

Screenshots/Recordings

Before

Simulator.Screen.Recording.-.iPhone.SE.3rd.generation.-.2024-11-13.at.17.58.39.mp4

After

Simulator.Screen.Recording.-.iPhone.SE.3rd.generation.-.2024-11-13.at.17.13.59.mp4

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 22bdd42
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0443ee8d-ff0f-4533-bfd7-b952eef39c2c

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 85b2157
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7aee3007-6d01-4d76-a800-8ef7db2fafb7

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[amitabh94]

LGTM!