Validate ShieldingTransfer in IBC VP

[yito88]

Describe your changes

ShieldingTransfer is set by IBC relayer(Hermes). IBC VP has to validate it for the IBC message.

Indicate on which release or other PRs this topic is based on

v0.39.0

Checklist before merging to draft

• I have added a changelog
• Git history is in acceptable state

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 113 lines in your changes missing coverage. Please review.

Project coverage is 53.87%. Comparing base (879a326) to head (0f5895d).
Report is 4 commits behind head on main.

Files	Patch %	Lines
crates/ibc/src/lib.rs	0.00%	113 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3431      +/-   ##
==========================================
- Coverage   53.92%   53.87%   -0.06%     
==========================================
  Files         317      317              
  Lines      107575   107670      +95     
==========================================
- Hits        58011    58005       -6     
- Misses      49564    49665     +101     

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

[sug0]

left a comment. btw, run_ledger_ibc_with_hermes is failing.

[sug0]

we're always falling back to nft transfers in case the port id is not for ics fungible token transfers. in case we receive a bogus port id, we strill try to validate the packet as an nft transfer. should we instead go case by case? even if here there are only 2 cases (transfer and nft transfer)

[grarco]

Putting a placeholder to prevent this pr from being merged while we understand and discuss some things offline

[yito88]

Thank you, Marco. The validation in this PR was duplicated and we need to check the MASP Transaction built by the relayer on the destination chain.