Support transparent and shielded resources combination in one transaction

[XuyangSong]

customer:
performer:
deadline: null
estimated: null
started: null
actual: null
completed: null
confirmed: null
dependencies:

• [ ]

---

In the end, we might wanna have a mix execution of transparent and shielded resources in one transaction. To make it happen, there are a bunch of compatibility issues to deal with, like merging fields, commitments, and all the mechanics between transparent and shielded resource management. We need a better spec to specify the details.

We also need to be careful about the privacy problems. related to anoma/taiga#161

We can discuss it during HH

[mariari]

I'm going to get this tracked in the specs and then we can make an actionable issue I'll message @XuyangSong directly for where it is later. I've already started the process.