Cannot borrow as a subtype if the capability was issued with multiple interfaces

[SupunS]

Current Behavior

More details on #3533 (comment)

resource interface I1: I2 {}

resource interface I2 {}

resource interface I3 {}

 resource R: I1, I2, I3 {}

// Case-1: Issue as `{I2}` only
// Below borrowing will pass
var a = self.account.capabilities.storage.issue<&{I2}>(/storage/r)
self.account.capabilities.publish(a, at: /public/a)

// Case-2: Issue as `{I2, I3}`.
// Below borrowing will fail
var a = self.account.capabilities.storage.issue<&{I2, I3}>(/storage/r)
self.account.capabilities.publish(a, at: /public/a)

// Borrow as `{I1}`
self.account.capabilities.borrow<&{I1}>(/public/a)!

Expected Behavior

Above should work.

Steps To Reproduce

See above

Environment

- Cadence version: latest
- Network: Testnet

[SupunS]

The exact hierarchy of interface in the use-case of https://discord.com/channels/613813861610684416/1273709822218473513 are:

                    (borrowed)     (issued)                       (issued)  
                   NFT.Receiver  ResolverCollection    aiSportsMinterCollectionPublic   
                        \              |                 /
 (issued)                \             |                /
NFT.CollectionPublic      \            |               /
                     \     \           |              /           
                       \    \          |             /
                          NFT.Collection            /
                                      \            /
                                       \          /
                                        Collection

So this is also a sibling issue, and is same as #3533

[bluesign]

ah this makes sense, I assumed, we made NFT.CollectionPublic: NFT.Receiver but it is not the case here. Maybe it is good idea to add that also to NFT standard.

[turbolent]

@SupunS So can we close this as a duplicate of #3533?

[SupunS]

Closing since this is same as #3533