refactor Transaction.createTransactionHash and add unit test for netw…

[evias]

Changed

• Refactor of Transaction.createTransactionHash for clarity and use protocol identical transaction creation flow as seen in TransactionExtensions

[coveralls]

Pull Request Test Coverage Report for Build 835

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 828:	0.0%
Covered Lines:	5
Relevant Lines:	5

---

💛 - Coveralls

[evias]

on hold because of Keccak usage in transaction hash, maybe not necessary will update PR accordingly

[rg911]

As gimre confirmed with me on slack, TransactionHash is always using sha3_256, I think we don't need resolving the signSchema anymore

[rg911]

I think we need remove the signSchema for generating TransactionHash and MerkleTransactionHash for now before we are more clear with all parties. Since the core devs confirmed that transactionHash only use sha3_256 regardless networkTypes (signSchema) at all