Equipping minted Name is silently blocked when it matches the current non-unique display name

### Build version
Not specified

### Issue Description
When a user has a non-unique display name set to a value (e.g. "test2000") and then mints a Name NFT with the exact same string, they are unable to equip that minted Name to their avatar. No error message or feedback is shown — the equip action simply does nothing. The workaround is to first change the non-unique name to something else, and then equip the minted Name.

This is particularly confusing for users who set their non-unique name early on and later mint a Name matching it, since they have no way of knowing why the equip is failing.

### STR (Steps to Reproduce)
1. Unequip any currently equipped Name from your avatar
2. Set non-unique display name to e.g. "test2000"
3. Mint a Name NFT with the same value "test2000"
4. Open the backpack and try to equip the newly minted Name

### Expected Result
The minted Name "test2000" should be equipped to the avatar successfully, replacing the non-unique display name.

### Actual Result with evidence
The equip action has no effect and no error or feedback is shown. The minted Name cannot be equipped unless the non-unique display name is first changed to a different value.

### Reproduction
Always (100%)

### Operative system and additional Notes
Windows

---
Reported by a user (via Dawid Krajewski)
Requested by Dawid Krajewski (<@U079GRD9WTZ>)

No source file or test is named. Reproduce issue #9550 through the backpack equip flow, then trace the handling of a minted Name that matches the non-unique display name. Done means the minted Name equips successfully and the silent failure is replaced with the expected outcome or feedback.

Written by the indexing model from the issue text.