Use owner event to populate ERC721 transfer topic

[codchen]

Describe your changes and provide context

PR sei-protocol/sei-wasmd#67 introduces a new event type indicating the pre-transfer owner of a CW721 token. This PR leverages the new event type to populate the owner topic of synthetic ERC721 transfer event correctly (previously it's set to the sender, which may be the spender and not the actual owner, and is against ERC721 convention).

Since events and receipts are not part of consensus state, this PR shouldn't be breaking app hash.

Testing performed to validate your change

unit test

[codecov]

Codecov Report

Attention: Patch coverage is 76.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 61.62%. Comparing base (e8e4b3b) to head (72f99e5).
Report is 208 commits behind head on main.

Files with missing lines	Patch %	Lines
app/receipt.go	76.00%	3 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1932      +/-   ##
==========================================
- Coverage   61.64%   61.62%   -0.03%     
==========================================
  Files         365      263     -102     
  Lines       26178    23395    -2783     
==========================================
- Hits        16138    14417    -1721     
+ Misses       8967     7973     -994     
+ Partials     1073     1005      -68     

Files with missing lines	Coverage Δ
app/receipt.go	79.15% <76.00%> (ø)

... and 217 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[philipsu522]

might be good to add a comment here re. why we're doing this - something like
"ERC721 standards dictate that the "sender" in the logs are the actual owner, and in cases where the owner is not the caller, we look for a matching token_id and extract the owner from synthetic events"

[philipsu522]

do we also test a transfer on behalf of someone else?

[stevenlanders]

should we log the error? (albeit rare/unlikely)

[dvli2007]

@codchen @stevenlanders @philipsu522 For CW721s, there is no "owner" attribute when a burn happens. You still will need to grab the "sender" attribute. I actually recommend you guys pull out the "burn" event mapping into its own case.

Edit: Nevermind. I see that wasmd is being modified to add an "owner" event for transfer_nft, send_nft, and burn actions.

Example of a burn: https://www.seiscan.app/pacific-1/txs/E95774B632C12AA9ABA5D5ACC36999C0EBD36612A8AC7C63199DCEB2993359FF~