System contracts should charge gas based on dispatched transactions

Problem

Currently, system contracts that dispatch transactions to other services for processing calculate gas independently of these calls. Alternatively, dispatched transactions can return the needed fees of all child transactions and the system contract can use this information to convert the returned fees into gas charges. This alternative will require less maintenance going forward and will result in more consistency in comparison to the equivalent HAPI call.

Solution

### Tasks
- [ ] Research current dispatch considerations
- [ ] support returning **all** builders created in the context of a dispatch, not just the builder for the dispatched transaction
- [ ] return the fees used by child transactions in builders when a transaction is dispatched
- [ ] convert the fees into gas and use this amount for gas requirements for the system contract
- [ ] remove existing code that calculate fees independently in dispatching system contracts.

Alternatives

No response

Begin by researching the current dispatch considerations and tracing how system contracts build dispatched transactions and calculate fees. The work is complete when all builders created during a dispatch are returned, child-transaction fees are converted into gas for system-contract requirements, and independent fee calculations are removed.