Do TLCC cc2scc calls require reflection in r/w set of transactions?

**Description**

Currently calls to TLCC from ECC (or potentially in the future for ERCC) are not reflected explicitly in an endorsement as other cc2(s)cc calls are. We should investigate whether this is secure and/or safe from conflicts and otherwise might have to extend our protocols. Probably also requires a bit more in-deptch study how fabric handles that exactly for other cc2scc calls.

Steps
- [x] for Tech preview milestone
- [x] investigate
- [x] update UML (see issue #355) as appropriate
- [ ] for [MVP milestone](https://github.com/hyperledger-labs/fabric-private-chaincode/milestone/38) if above implies implementation changes
- [ ] update Project planning [GDocs](https://docs.google.com/document/d/1qpOIIky0AVeCpzuxBVwlE1XIWPhRjL-NzrQlfF4C0Tk/edit#heading=h.j2upfqf74u3y) and
[Mural](https://app.mural.co/t/fpc5303/m/fpc5303/1591259633756/cad0b8be3197d0d55a6000298d801f406757421a) as appropriate
- [ ] implement it ...

**Link to feature or bug**

**Link to dependent issues**