Better Display of the different types of Contract Events

[DOBEN]

Task description

Block explorers often distinguish between top-level transactions and internal transactions.

CCDScan currently displays all contractTraceEvents and contractEvents in one table.

A better/clearer separation would be beneficial. One option to apply the concept would be two tables:

top-level transactions = ContractTraceElement::Updated; and contract initialized transaction events
internal transactions = ContractTraceElement::Interrupted; ContractTraceElement::Transferred; ContractTraceElement::Resume; ContractTraceElement::Upgraded

[limemloh]

Interaction with other smart contracts within a top level transaction will also result in ContractTraceElement::Updated and should maybe be considered an 'internal transaction' as well.