fix(core-api): include multipayment in forged amount

[rainydio]

Summary

Fixes #3495

Block totalAmount property is signed and is used to checksum database. It cannot be changed to include multipayment transactions without milestone. So this is implemented on API level, but things there aren't that simple either.

I cannot simply pull all transactions with every block that is loaded from database. Otherwise this will significantly stress database on /blocks and /blocks/search endpoints. Second there is raw=true parameter which presumably still has to return raw block data that can be used to check signature (so without multipayment included in total).

1. BlockHistoryService now has capability of joining transactions (...byCriteriaJoinTransactions methods).
2. New BlockWithTransactionsResource was added. Only its transform method is used which walks through transactions and calculates forged total that includes multipayment.
3. All of transformed BlockResource usages are now using BlockWithTransactionsResource.
4. Those usages requiring transformed BlockWithTransactionsResource use new ..byCriteriaJoinTransactions methods to also join multipayment transactions only so forged total includes multipayment transactions.

Checklist

• Tests
• Ready to be merged

[faustbrian]

@rainydio conflicts