fix: refresh ownership status for nfts

[sahar-fehri]

Description

When a user transfers an NFT, he will still be able to see it on the NFT tab view.
This PR refreshes the NFTs owned by the user and displays only the ones currently owned by him.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MMASSETS-103

Manual testing steps

1. Mint an NFT using one of your accounts(ACC1).
2. Go to NFTs tab and make sure you can see your minted NFT.
3. Transfer the NFT to another account (ACC2), i used REMIX solidity IDE to deploy my contract and transfer the NFT.
4. Go to the account you sent the NFT to (ACC2)
5. Import NFT (enter address and tokenId)
6. Make sure you can see the NFT sent by ACC1
7. Go back to NFTs tab on ACC1 and make sure you no longuer see the NFT in your list

Screenshots/Recordings

Before

Account2 transferred the three nfts to Account test, and yet you still see the nfts displayed on account2.

Screen.Recording.2024-01-09.at.19.04.20.mov

After

Returning to account2 and refreshing the page, will remove the nft from the list.

final4.mov

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.

[sahar-fehri]

I have read the CLA Document and I hereby sign the CLA

[codecov-commenter]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (b2c9d98) 39.64% compared to head (65969eb) 39.64%.
Report is 10 commits behind head on main.

Files	Patch %	Lines
app/components/UI/CollectibleContracts/index.js	0.00%	4 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8230   +/-   ##
=======================================
  Coverage   39.64%   39.64%           
=======================================
  Files        1233     1233           
  Lines       29830    29822    -8     
  Branches     2840     2840           
=======================================
- Hits        11826    11824    -2     
+ Misses      17315    17309    -6     
  Partials      689      689           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8b7371f9-a52f-4f8d-a736-65132be7d714
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[sethkfman]

LGTM

[cortisiko]

hey @sahar-fehri can we confirm this also works on android? If possible can you add unit test coverage for this particular flow?

Also can you confirm that this bug no longer exists on your PR: #3406

[sahar-fehri]

hey @sahar-fehri can we confirm this also works on android? If possible can you add unit test coverage for this particular flow?

Also can you confirm that this bug no longer exists on your PR: #3406

hey @cortisiko I have tested it on Android also, no issues. I have added a unit test for my change, also i dnt see the problem described on PR: #3406 on my PR 🙏

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
50.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sethkfman]

LGTM

[cortisiko]

✅ ✅ ✅ ✅ ✅