fix: blocked by peer status

[lorux0]

What does this PR change?

Re-enables the propagation of the blocked list through comms and improves UI (user context menu & passport) flows when the peer has blocked you.
NOTE: it may have an impact in the comms infra throughput/costs.

How to test the changes?

1. Launch the explorer
2. Block a user or get blocked by a user
3. Check that the flows in the passport are correct. If the user has blocked you, you shouldn't be able to interact. If you blocked the user, you should be able to unblock it
4. Open any user context menu. If the user has blocked you, you shouldn't be able to interact, for example send a friend request. If you blocked the user, you should be able to unblock it
5. Try send messages. You shouldn't be able to receive or send to/from blocked users.

Our Code Review Standards

https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

Copilot summary

🤖 Generated by Copilot at 758c31c

This pull request fixes the blocked status propagation in the comms layer and updates the passport and user context menu UIs to reflect the blocked status of the user and the peer. It renames the field hasBlocked to isBlockedByPeer in the PlayerPassportModel and the PassportPlayerInfoComponentController classes, and uses the blocked status from the comms layer and the user profile model in the PassportPlayerInfoComponentView and the UserContextMenu classes. It also comments out the lines that clear the blocked and muted lists of the user profile in the sagas.ts file.

[github-actions]

After the CI passes:

Web

This branch can be previewed at:

• https://play.decentraland.org/?explorer-branch=feat/blocked-friend-requests
• https://play.decentraland.zone/?explorer-branch=feat/blocked-friend-requests

Desktop:

If you have the launcher installed (download launcher) you can press open on the following link:

• Open custom protocol
• Open custom protocol with Developer Mode

SDK 6/7:

• Open SDK7 scenes playground
• Open SDK7 scenes in preview
• Open SDK6 scenes in preview

More

• Code coverage report: https://renderer-artifacts.decentraland.org/branch-coverage/feat/blocked-friend-requests
• Benchmark report: https://renderer-artifacts.decentraland.org/branch-benchmark/feat/blocked-friend-requests/index.html

[hugoArregui]

can't messages be ignored locally instead? I'm worried about the big warning above

[lorux0]

Can you please elaborate?

[hugoArregui]

I meant the warning in the comment "the blocked and muted sizes are too big for the network", can we simply ignore the messages if we get one from a blocked user?

[lorux0]

Is not only the chat messages. You shouldnt be able to interact with friend requests or preview the passport of peers that blocked you. We have special states in the UI for this.

[hugoArregui]

ok, understood, but I don't think we can simply send this through comms, some users have thousands of addresses in the block list, and this message is broadcasted to everyone around the user.

[lorux0]

I will try to make a workaround by fetching the user profile from the catalyst when this information is required

[lorux0]

Trying to fetch the blocked list from the catalyst when needed adds too much complexity thus a mess to handle with the current architecture. A new proposal is coming on which profile information will always be fetched from the catalyst instead of being broadcasted through comms. This way would fix the problem